Configuration in project.xml change

[Laurent Forêt]

Hello,

While introducing settings in project configuration I have changed the element name of the descriptor file. The old ivy projects extended will crash :

the project configuration :
<project xmlns="http://www.netbeans.org/ns/project/1">
    <type>org.netbeans.modules.java.j2seproject</type>
    <configuration>
...
        <ivyConfiguration xmlns="http://code.google.com/p/ivybeans/ns/ivy-module/1">
            <ivyFile>ivy.xml</ivyFile>
        </ivyConfiguration>
    </configuration>
</project>

becomes :

<project xmlns="http://www.netbeans.org/ns/project/1">
    <type>org.netbeans.modules.java.j2seproject</type>
    <configuration>
...
        <ivyConfiguration xmlns="http://code.google.com/p/ivybeans/ns/ivy-module/1">
            <descriptorFile>ivy.xml</descriptorFile>
            <settingsFile>ivysettings.xml</settingsFile>
        </ivyConfiguration>
    </configuration>
</project>

Laurent

[Paulo Siqueira]

Now it compiles with the configuration from SVN =)
(but with 14 warnings)

One question:

I noticed that genfiles.properties and build-impl.xml are committed.
Since NetBeans generates then, do they need to be in the source repository? We don't do it in our projects here, but maybe it makes no difference at all... I'm just curious =)

[]s,

--
Paulo R C Siqueira
SCJP / SCWCD
http://www.ipti.org.br
Contato: (11) 8149-5046

[Laurent Forêt]

Ok ! I have committed the corrections for compile warnings (revision 80).

the genfiles.properties is an accident. And the build-impl.xml is a good remark.

Laurent

[Paulo Siqueira]

I don't know if it is important, but I still see these:

verify-class-linkage:
Warning: org.apache.ivy.Main cannot access org.apache.commons.cli.Options
Warning: org.apache.ivy.Main cannot access org.apache.commons.cli.GnuParser
Warning: org.apache.ivy.Main cannot access org.apache.commons.cli.ParseException
Warning: org.apache.ivy.Main cannot access org.apache.commons.cli.HelpFormatter
Warning: org.apache.ivy.Main cannot access org.apache.commons.cli.OptionBuilder
Warning: org.apache.ivy.Main cannot access org.apache.commons.cli.CommandLineParser
Warning: org.apache.ivy.Main cannot access org.apache.commons.cli.CommandLine
Warning: org.apache.ivy.ant.AddPathTask cannot access org.apache.tools.ant.types.Path
Warning: org.apache.ivy.ant.AddPathTask cannot access org.apache.tools.ant.BuildException
Warning: org.apache.ivy.ant.AddPathTask cannot access org.apache.tools.ant.Task
(additional warnings not reported)

plus 13 compile warnings, when running "Clean and Build All" on Ivybeans

[]s,

[Laurent Forêt]

For instance we do not care that the Main class does not find the CLI library. And ant libs are available in runtime. The Ivy libs used for instance is the beta,  waiting for fhe final release.

Now in the trunk we have something runnable and testable.

Laurent.