On 5/03/2016 11:50 PM, Claes Redestad wrote:
Hi,
similar issues were discovered too late to stop b108, e.g.,
https://bugs.openjdk.java.net/browse/JDK-8150920. Fix is already in jdk9/dev,
so I think the next build should be more well-behaved and hope we can provide
it more promptly than normal
Hi,
I would like to request open source licenses for Intellij in the name of the
Apache Ant project.
Who is interested ?
Best regards,
Antoine
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e
I like the idea of Michael to develop on the master branch against Java 1.8 and
to have a long term support branch for Java 1.6 or Java 1.7.
Yes that would increase the amount of time needed to make releases.
We might not necessarily release both builds at the same time every time since
the Ja
I personally don't think we should constrain ourselves to supporting End of
Life'd versions of Java: anyone wanting to use an older version of Java can
download an older version of Ant. That being said, Ant doesn't introduce
major new features particularly often so we may not be losing too much by
Consider Enterprise is often 2 versions (maybe 3 versions) behind latest JDK,
at lease based on my own experience, so 7 should still be included?
Sent from my tablet
> On Mar 6, 2016, at 10:31, Fernando Cassia wrote:
>
>> On 3/6/16, Stefan Bodewig wrote:
>> I think it's time to drop support f
On Mar 6, 2016 4:12 AM, "Stefan Bodewig" wrote:
>
> I'm not sure whether moving to Java6 is worth the effort since it has
> been EOLed as well, even Java7 is no longer officially supported by
> Oracle, but personally I wouldn't want to require Java8 right now.
Java 1.6 extended support lasts til D
On 3/6/16, Stefan Bodewig wrote:
> I think it's time to drop support for Java5 and - as we've done in the
> past - bump the second part of Ant's version number to reflect the
> change.
+1
> I'm not sure whether moving to Java6 is worth the effort since it has
> been EOLed as well, even Java7 is
Github user bodewig commented on the pull request:
https://github.com/apache/ant/pull/15#issuecomment-192895174
don't worry and thanks for your support
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user tzezula commented on the pull request:
https://github.com/apache/ant/pull/15#issuecomment-192894935
Sorry for that. I will get some Windows box for testing.
Yes, it's '/'.
The -m option support eitheror /.
---
If your project is set up for it, you can reply to
Github user bodewig commented on the pull request:
https://github.com/apache/ant/pull/15#issuecomment-192893331
Great.
Our [CI builds](https://builds.apache.org/job/Ant-Build-Matrix/) on Windows
are failing because the test `testModuleAndClassnameCommandLine` expects the
modu
Github user tzezula commented on the pull request:
https://github.com/apache/ant/pull/15#issuecomment-192890123
Thanks Stefan, I will do a patch of Ant's java task manual.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user asfgit closed the pull request at:
https://github.com/apache/ant/pull/15
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled
Github user bodewig commented on the pull request:
https://github.com/apache/ant/pull/15#issuecomment-192878534
Thanks a lot Tomas, I've merged your patch.
It would be good if you could also provide a patch the java task page
inside of Ant's manual.
---
If your project is se
Hi all
it looks as if we need to make a bunch of changes in order to support
Java9. Right now we can't even bootstrap ant on Java9 without changes
since javac doesn't support -target 1.5 anymore.
I think it's time to drop support for Java5 and - as we've done in the
past - bump the second part of
Hi Tomas
welcome to the dev list.
On 2016-03-03, Tomas Zezula wrote:
> I am working on the NetBeans Ant based project. For the upcoming
> NetBeans release I need to update the NetBeans generated build scripts
> to support the JDK 9 module system. The most problematic is the Java
> task which nee
> > > This is why I put the Ant developers in CC. The correct way would be
> > > to look at the *decoded* path (not just getPath() because this is also
> > > one of the "famous" traps in the URL class - one reason why it should
> > > be avoided in favor of URI). URL.toURI().getPath() is most safe t
16 matches
Mail list logo
