Re: [JPP-Devel] Jar manifest file and classpath

2007-10-29 Thread Paul Austin
If we have decided to include functionality that requires the most recent version of ant we should just include a note in the build instructions that ant 1.7 is required and leave it at that. I don't think we should have two build files as it's unlikely that anyone will remember to clean it up in a

Re: [JPP-Devel] Jar manifest file and classpath

2007-10-29 Thread Sunburned Surveyor
Stefan's idea on the name of the script sounds good to me. Landon On 10/28/07, Andreas Schmitz <[EMAIL PROTECTED]> wrote: > Stefan Steiniger wrote: > > Hi, > > > does it makes sense to add your built script to repository but renaming > > it to "built_ant17.xml"? > > so that the old one is still t

Re: [JPP-Devel] Jar manifest file and classpath

2007-10-28 Thread Andreas Schmitz
Stefan Steiniger wrote: Hi, > does it makes sense to add your built script to repository but renaming > it to "built_ant17.xml"? > so that the old one is still there for a year or so? > Or we do it the other way around. But then i am not sure if the nightly > built still works. > We should make a

Re: [JPP-Devel] Jar manifest file and classpath

2007-10-28 Thread Stefan Steiniger
Hei Andreas, does it makes sense to add your built script to repository but renaming it to "built_ant17.xml"? so that the old one is still there for a year or so? Or we do it the other way around. But then i am not sure if the nightly built still works. We should make a notice to the tracker it

Re: [JPP-Devel] Jar manifest file and classpath

2007-10-25 Thread Paul Austin
I had a brainwave last night. A maven repository is just a bunch of files and directories on a server. The most recent subversion content can be viewed via HTPP as a bunch of files and directories. Therefore we can just create a new subversion module for our repository and check files into that. T

Re: [JPP-Devel] Jar manifest file and classpath

2007-10-25 Thread Andreas Schmitz
Paul Austin wrote: Hi, > I have modified the pom so that it now compiles, I made a change that I > thought was required for the classpath but that just meant it didn't > download any of the jars. very cool, thanks. I've added a main class manifest entry to the .jar, now you can use java -jar ope

Re: [JPP-Devel] Jar manifest file and classpath

2007-10-24 Thread Sunburned Surveyor
Thanks for the information on Netbeans Malte. The Sunburned Surveyor On 10/24/07, Malte Weller <[EMAIL PROTECTED]> wrote: > Hi Landon, > > NetBeans 6.0 is also using Ant 1.7 and if we need a newer one I can > update to this version in NetBeans too. > How about that in Eclipse ? ;-) > > Malte > >

Re: [JPP-Devel] Jar manifest file and classpath

2007-10-24 Thread Paul Austin
Andreas, I have modified the pom so that it now compiles, I made a change that I thought was required for the classpath but that just meant it didn't download any of the jars. Also I've added a few jars on my own repository that aren't anywhere else. We should look at setting up an open jump repo

Re: [JPP-Devel] Jar manifest file and classpath

2007-10-24 Thread Andreas Schmitz
Paul Austin wrote: Hi, > I have added this to the maven build script that I created for OpenJUMP. > > The advantage with the maven one is it will automatically update it > based on the dependencies in the build script. do I need something besides maven to get the maven script to work? A "mvn ins

Re: [JPP-Devel] Jar manifest file and classpath

2007-10-24 Thread Malte Weller
Hi Landon, NetBeans 6.0 is also using Ant 1.7 and if we need a newer one I can update to this version in NetBeans too. How about that in Eclipse ? ;-) Malte Andreas, It seems from this link: http://www.thecrumb.com/2007/07/19/ant-version-16x-vs-17x-and-eclipse-33/ that Eclipse 3.3 is usi

Re: [JPP-Devel] Jar manifest file and classpath

2007-10-23 Thread Andreas Schmitz
Paul Austin wrote: Hi, > I have added this to the maven build script that I created for OpenJUMP. > > The advantage with the maven one is it will automatically update it > based on the dependencies in the build script. thanks. That would be good enough for me ;-) Is that enough to close the iss

Re: [JPP-Devel] Jar manifest file and classpath

2007-10-23 Thread Paul Austin
Andreas, I have added this to the maven build script that I created for OpenJUMP. The advantage with the maven one is it will automatically update it based on the dependencies in the build script. Paul Andreas Schmitz wrote: > Hi list, > > I've just managed to get issue > http://sourceforge.net

Re: [JPP-Devel] Jar manifest file and classpath

2007-10-23 Thread Sunburned Surveyor
Andreas, It seems from this link: http://www.thecrumb.com/2007/07/19/ant-version-16x-vs-17x-and-eclipse-33/ that Eclipse 3.3 is using Ant 1.7. I haven't been able to confirm what version of Ant Netbeans 6.0 is using. I don't have a problem moving up to Ant 1.7, but it would be nice if the two m

[JPP-Devel] Jar manifest file and classpath

2007-10-23 Thread Andreas Schmitz
Hi list, I've just managed to get issue http://sourceforge.net/tracker/index.php?func=detail&aid=1475028&group_id=118054&atid=679906 working. I've added a section to the jar task, and I'm using the task to set up the manifest Class-Path attribute. The only downside is that the manifestclasspath