Sounds good. Similar to Ant, on branch for maintaining the version for the old
Java version and master for the new(er) one.
And as suggested we shoundn't go farer than Ant itself, so Java8 is fine with
me (no Java 13).
So: +1
Jan
> -Ursprüngliche Nachricht-
> Von: Jaikiran Pai
nd a place where this private field is read...
Jan
> -Ursprüngliche Nachricht-
> Von: Jan Matèrne (jhm) [mailto:apa...@materne.de]
> Gesendet: Dienstag, 29. Oktober 2019 08:48
> An: 'Ant Developers List'
> Betreff: AW: Script task specification
>
> I placed
UILD FAILED
C:\projekte\apache-ant-svn\sandbox\script\build.xml:9:
org.mozilla.javascript.EcmaError: ReferenceError: "foo" is not defined.
Jan
> -Ursprüngliche Nachricht-----
> Von: Jan Matèrne (jhm) [mailto:apa...@materne.de]
> Gesendet: Dienstag, 29. Oktober 2019 08:03
>
It seems that the task must be executed before.
If you add a >depends="sub"< on the main target, that works.
So the question is: when are id's stored?
The parsing is done via ProjectHelper's and their SAX-Parser-Handlers.
On the first view I would say, that the id is stored while parsing - so
> > Just a question: there is a file fr\jayasoft\ivy\ant\antlib.xml which
> seems to be a copy of org\apache\ivy\ant\antlib.xml. Is it for BWC?
> Yes, looks like it.
> https://github.com/apache/ant-ivy/blob/master/build.xml#L263. It was
> done way back in 2007 and I don't think anyone uses that
done
Jan
> -Ursprüngliche Nachricht-
> Von: Jaikiran Pai [mailto:jaiki...@apache.org]
> Gesendet: Donnerstag, 24. Oktober 2019 13:42
> An: Ant Developers List
> Betreff: Need help releasing IVY project in JIRA
>
> It looks like I don't have relevant permissions in JIRA to release the
>
Checked the bin.zip.
Seems to be ok.
Just a question: there is a file fr\jayasoft\ivy\ant\antlib.xml which seems to
be a copy of org\apache\ivy\ant\antlib.xml. Is it for BWC?
Hello-Ivy-Example:
- run with "ant -lib ..\..\..\ivy-2.5.0.jar run"
--> Ivy starts
--> Ivy vesion 2.5.0
--> Problems
It's more a Windows related question than an Ant one.
This message occurs with nearly every zip.
Solution seems to be registering your IPs as "secure".
https://superuser.com/questions/1231191/how-to-disable-zip-file-security-warning
> > It's been some months now since our last 1.9.x and 1.10.x Ant
> releases.
> > During that period, we have added some good number of fixes and
> > enhancements to both these versions upstream. Some of the users (in
> > bugzilla discussions) have asked if we can do a release sooner to get
> >
+1, as I think there aren't many users; and we could reactivate it on demand
Jan
> -Ursprüngliche Nachricht-
> Von: Jaikiran Pai [mailto:jaiki...@apache.org]
> Gesendet: Samstag, 22. Dezember 2018 03:16
> An: Ant Developers List
> Betreff: Re: [VOTE] Retire Antlib SVN
>
> An implicit
Retiring a part of a top level project is much easier than retiring the TLP
itself.
We have created a "process" while archiving EasyAnt & Co:
http://ant.apache.org/processes.html#Retire%20a%20subproject%20or%20component
Basically
* PMC vote for retiring the thing
* make resources read-only (code,
+1 We are neither the first nor the only project which should migrate, so it
should work smoothly. ;-) TODOs: change local remote urls, update Jenkins jobs,
update homepage
Jan
> -Ursprüngliche Nachricht-
> Von: Jaikiran Pai [mailto:jaiki...@apache.org]
> Gesendet: Samstag, 8.
Thank you for your suggestion.
But I think we shouldn’t add a new dependency for replacing code, that works
and was touched last time 8 months ago ('just' introducing some Java8 stuff),
then 2 years ago (no FileInput/OutputStream::new) then 4 years ago ...
So maintenance is no real point here.
If I understand Dragans point right, the warning comes when analyzing the code.
Not just running Ivy.
So the normal user won't see the warning. Maybe we should implement a warning?
Jan
> -Ursprüngliche Nachricht-
> Von: Jaikiran Pai [mailto:jaiki...@apache.org]
> Gesendet: Mittwoch, 10.
Jan and Jaikiran,
> > >
> > > looks like IvyDE trunk build needs attention, too (SSL protocol
> > > failure when resolving Checkstyle).
> > >
> > > Thanks, Gintas
> > >
> > > On Wed, 8 Aug 2018 at 13:23, Jan Matèrne (jhm)
>
st
> Betreff: Re: IVYDE-379
>
> Thanks, Jan, most locations look good, though Ivy still refers to
> Subversion. I'll check again tomorrow.
>
> Gintas
>
> On Wed, 8 Aug 2018 at 12:57, Jan Matèrne (jhm)
> wrote:
>
> > Changed in SVN.
> > 'Our' locations
Tried to change from "Ant 1.9.9" to "Ant (latest)".
An "Ant 1.10.1" or an "Ant 1.9.9" are the latest available named versions.
Got an
Access denied
This job's current authorization strategy does not permit jhm to modify the
job configuration
Asked
Changed in SVN.
'Our' locations are now:
https://ant.apache.org/doap_Ant.rdf
https://ant.apache.org/antlibs/antunit/doap_AntUnit.rdf
https://ant.apache.org/antlibs/compress/doap_CompressAntlib.rdf
https://ant.apache.org/antlibs/dotnet/doap_DotnetAntlib.rdf
Sv1.2 parameter.
Job restarted.
Jan
> -Ursprüngliche Nachricht-----
> Von: Jan Matèrne (jhm) [mailto:apa...@materne.de]
> Gesendet: Sonntag, 22. Juli 2018 12:54
> An: 'Ant Developers List'
> Betreff: AW: Jenkins-Builds failing
>
> Checked by myself that a PMC chair co
elopers List
> Betreff: Re: Jenkins-Builds failing
>
> Should we ask infra if nobody else knows about Jenkins authorization?
>
> Gintas
>
> On Fri, 20 Jul 2018 at 11:26, Jan Matèrne (jhm)
> wrote:
>
> > Neither do I.
> >
> > Jan
> >
> > > -
Neither do I.
Jan
> -Ursprüngliche Nachricht-
> Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
> Gesendet: Freitag, 20. Juli 2018 10:15
> An: dev@ant.apache.org
> Betreff: Re: Jenkins-Builds failing
>
> Now that I checked the job's logs, I think that's true. We had this
> issue in
Ursprüngliche Nachricht-
> Von: Jan Matèrne (jhm) [mailto:apa...@materne.de]
> Gesendet: Dienstag, 3. Juli 2018 07:43
> An: 'Ant Developers List'
> Betreff: AW: ant task mail fails on jdk10
>
> We already have something:
> mail: "This task may depend on external libra
We already have something:
mail: "This task may depend on external libraries that are not included in
the Ant distribution. See Library Dependencies for more information."
dependencies:
"mail.jar Mail task with Mime encoding, and the MimeMail task
mail, jira...)
Jan
> -Ursprüngliche Nachricht-
> Von: Jan Matèrne (jhm) [mailto:apa...@materne.de]
> Gesendet: Sonntag, 1. Juli 2018 21:30
> An: 'Ant Developers List'
> Betreff: AW: Testing IvyDE
>
> > It looks like Ant nightly is stuck (possibly due to plugin update
> It looks like Ant nightly is stuck (possibly due to plugin update in
> Jenkins) and it's blocking all other builds.
>
> Gintas
I can't do it myself so I'll ask for killing the job.
Jan
-
To unsubscribe, e-mail:
Thanks, will have a look tomorrow.
Sounds like we should keep BZ as it is.
Jan
> -Ursprüngliche Nachricht-
> Von: Stefan Bodewig [mailto:bode...@apache.org]
> Gesendet: Donnerstag, 28. Juni 2018 13:27
> An: dev@ant.apache.org
> Betreff: Re: [Bug 33169] KIndly update the date feature
>
>
> > Just curious about our bugzilla infrastructure - do random users get
> > to change the content of these bugs, even if they aren't the ones who
> > reported the issue?
>
> Yes.
>
> Back when Bugzilla was introduced the developers and admins falsely
> assumed only sensible people would be
Changing Ants own test to use JUnit5 does not mean we have to change Ant itself
and don't have to cut a release.
What do you want to move to "ant-legacy"?
Jan
> -Ursprüngliche Nachricht-
> Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com]
> Gesendet: Donnerstag, 3. Mai 2018
> > In my eyes most of the committers don't like these "code style"
> changes.
> > So please stop these changes and invest your energy more productive.
> >
> > I don't think it would be helpful if another committer starts
> > reverting the changes because of a different preference ...
>
>
> With
> > Changes like these are random personal preferences.
>
> Right.
>
> > The fact that these are being done even after the mail discussions we
> > recently had, indicates that the request to not do such changes have
> > been ignored. This is going down the route of a being some kind of a
> >
Why not an assert with a meaningful message to test if the property is set?
Jan
> -Ursprüngliche Nachricht-
> Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com]
> Gesendet: Freitag, 20. April 2018 10:42
> An: Ant Developers List
> Betreff: Re: Ant JUnit tests
>
> Assumption is
I dont see the automatic snapshots as a problem.
We should not ask "all" users to use them, but for single users that may be ok.
They are "testing" (means DEV) the current/upcoming version against their
(problematic) scenario.
Jan
> -Ursprüngliche Nachricht-
> Von: Gintautas
May /docs-to-convert ;)
A directory /doc makes the expectation to find (actual) documentation.
Jan
> -Ursprüngliche Nachricht-
> Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com]
> Gesendet: Dienstag, 13. März 2018 10:14
> An: Ant Developers List
> Betreff: Re: Ivy old docs
If the /doc directory is not maintained any more and all sources are now in
/asciidoc, it should be deleted.
If the /asciidoc/dev/makerelease.adoc is uptodate, feel free to change the
/ReleaseInstrutions to point there.
Jan
> -Ursprüngliche Nachricht-
> Von: twogee
> > > > I made an attempt to convert the manual to HTML 5, the rationale
> > > being
> > > > that HTML 5 deprecates tt tag and recommends to replace it with
> > > > tags like code, kbd, samp and var, which could be used in a more
> > > consistent
> > > > way to achieve something closer to a
> > I made an attempt to convert the manual to HTML 5, the rationale
> being
> > that HTML 5 deprecates tt tag and recommends to replace it with tags
> > like code, kbd, samp and var, which could be used in a more
> consistent
> > way to achieve something closer to a semantic markup.
> >
> > I
@Stefan: You added the 1.9 manual. Do you think we could upate the manuals this
way?
Jan
> -Ursprüngliche Nachricht-
> Log:
> new target for updating the (online)manual from Ant's git-repo
>
> Modified: ant/site/ant/build.xml
> URL:
>
> Creating new git repos on apache is self-serve, so it's just as easy as
> GitHub really (though you need to be a PMC member I think).
>
> On 28 February 2018 at 12:48, Jan Matèrne (jhm) <apa...@materne.de>
> wrote:
>
> > > > If we want to migrate the
> > If we want to migrate the site repo, we should also think about
> > handling the sandbox.
>
> I think we just never migrated it because it simply wasn't used. Using
> a single git repository for several unrelated experiments doesn't sound
> very git-like.
Yep.
We could migrate site to git
ring that on purpose :-) see my previous e-mails regarding
> FishEye links or "Related Projects".
> Any chance of splitting of site sources to Git and using SVN for
> publication only?
>
> Gintas
>
> 2018-02-26 8:10 GMT+01:00 Jan Matèrne (jhm) <apa...@materne.de&
Have you seen doc/dev/makerelease.html ?
But updating (and maybe automating) is a good idea. ;)
Jan
> -Ursprüngliche Nachricht-
> Von: jaiki...@apache.org [mailto:jaiki...@apache.org]
> Gesendet: Dienstag, 27. Februar 2018 13:59
> An: notificati...@ant.apache.org
> Betreff: ant-ivy git
> We used to do so, even cut beta releases so people could test them
> years ago. Back then nobody tried the betas so we stopped doing them.
> I'm not saying we shouldn't include the user mailing list, let's just
> do that. I'm just a bit pessimistic this would have caught the problem.
Ok, but
+1
We could post this info to users@ too and ask for feedback.
(Have to update the ReleaseInstructions on #14 ;)
Jan
> Our recent release of Ant showed up a major issue[1] which impact Ant
> users. The issue was found almost as soon as Ant was released, thanks
> to the user upgrading to this
> What this specific test failure shows, though, is that we now no longer
> are able to distinguish between a resource that we could copy but can't
> because it doesn't provide a name and the case of "all resources have
> been stripped out by mappers as "I don't know how to handle it".
*
CVE-2017-5645: Apache Ant 1.9.9 and 1.10.1 - Apache Log4j 1.2.13 security
vulnerability
Severity: low
Vendor: The Apache Software Foundation
Versions Affected:
Apache Ant 1.9.0 - 1.9.9
Apache Ant 1.10.0 - 1.10.1
The unsupported Apache Ant 1.8 and lower versions are also affected.
+1
Jan
> -Ursprüngliche Nachricht-
> Von: Stefan Bodewig [mailto:bode...@apache.org]
> Gesendet: Samstag, 3. Februar 2018 18:07
> An: dev@ant.apache.org
> Betreff: [VOTE] Release Apache Ant 1.10.2 based on RC1
>
> Hi all
>
> I've created a release candidate for 1.10.2:
>
> git tag:
+1
Jan
https://dist.apache.org/repos/dist/dev/ant/manual/ does not contain the manual
for 1.10.2, only 1.9.10.
Try apache-ant-1.9.10 on Java7
- ant -f fetch.xml all -Ddest=system
==> works, but downloading JAI fails:
Downloading: javax/media/jai-core/1.1.3/jai-core-1.1.3.pom from
> Well, the task wil not work with any future Java releases since the
> internal APIs are not comming back.
>
> Meanwhile, a quick search shows that while there is quite a lot
> activity with image io, there is no equivalent of JAI.create() for
> image transformations (on which the image task is
> We should probably mention the deprecation of the log4j logger and the
> changes required to support the log4j2 bridge in WHATSNEW as well.
Done. Marked as "breaking BWC".
Jan
-
To unsubscribe, e-mail:
Re: Ant Nightly Build Job in Jenkins
>
> On 2018-01-28, Stefan Bodewig wrote:
>
> > On 2018-01-28, Jan Matèrne (jhm) wrote:
>
> >> Updated the target to use actual 2.5.8. But there is still a
> problem
> >> when using two formatters, so I commented the txt-
Updated the target to use actual 2.5.8.
But there is still a problem when using two formatters, so I commented the
txt-formatter out.
Jan
> -Ursprüngliche Nachricht-
> Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com]
> Gesendet: Samstag, 27. Januar 2018 19:16
> An: Ant
Cool. ;)
Have committed my hint to the manual.
Nothing more in my pipeline ...
Jan
> -Ursprüngliche Nachricht-
> Von: Stefan Bodewig [mailto:bode...@apache.org]
> Gesendet: Freitag, 26. Januar 2018 18:45
> An: dev@ant.apache.org
> Betreff: Cutting new releases?
>
> Hi all
>
> while
> What must be done to complete the work on SVG (IVY-922/IVY-450 or resp
> PR-55/PR-60)? If you fine with merging (eventually adjusting the
> contents of SVG), let's do it.
I added a comment on the PR.
For short:
- license header is missed on two files
- improve two JavaDocs
- test: does the
I took my old TODO list for Ivy-2.5.0.
Most of them are still open, how to deal with that?
In my opinion we should try to get a release out and postpone these to a
2.5.1 (means reducing stopper->later).
We have lots of changes we could deliver in this way. We also show a sign of
life in that
IMO catching an exception only makes sense if you check that exception against
certain assumptions or you expect that.
Otherwise the test runner will catch that (not excepted) and mark the test as
failed.
If the current codebase differs from that, I would agree with simplifying that.
Jan
>
[
https://issues.apache.org/jira/browse/IVY-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16223993#comment-16223993
]
Simon Ochsenreither commented on IVY-1502:
------
Hi [~jhm], I have reviewed the code that implements th
> I'm closing in on IVY-1420; it's Willem's patch + writeInheritedItems
> for entire inherited configurations/dependencies blocks (and another
> test case for that).
good.
> PR-57 breaks BC but mitigates that except for a special case. Anyway,
> why must every release be a drop-in replacement
I recap the todo list before a 2.5.0 release:
- https://issues.apache.org/jira/browse/IVY-1485
Incorrect revision of dependencies put in to delivered Ivy files
Status: Jaikiran wanted to focus on that (11.09.2017)
prio: stopper ("but it was IVY-1485 which reanimated the community")
-
This would break BC of the website ...
Ok, I am joking. This is daily business with websites ;)
I think we dont even need a 301-permantent-redirect and following the W3C
recommendations would be fine.
Jan
> -Ursprüngliche Nachricht-
> Von: Gintautas Grigelionis
If the new Java version supports the symlink creation and it's an
implementation detail
of Ivy (so not part of an API other could use) I am in favour of getting rid of
the old
implementation.
Getting rid of that means being more standard compliant and having less to
maintain. ;)
Jan
>
While it's fine to have such a dynamic behaviour it's hard to maintain.
On this special location - is it really required or could we use a fixed
version
(like current HttpComponents Client)
https://hc.apache.org/:
"HttpComponents Client is a successor of and replacement for Commons
Maybe you could set the timeout strategy globally:
/ivysettings/resolvers/@timeout-constraint
...
Jan
> -Ursprüngliche Nachricht-
> Von: jai.forums2...@gmail.com [mailto:jai.forums2...@gmail.com]
> Gesendet: Montag, 17. Juli 2017 06:56
> An:
summa summarum +2 ;-)
Jan
> -Ursprüngliche Nachricht-
> Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com]
> Gesendet: Dienstag, 11. Juli 2017 23:24
> An: Ant Developers List
> Betreff: Re: [VOTE] IvyDE requirements
>
> +1 on both (having suggested it previously).
>
> Gintas
>
> >>> I was reading up some docs and happened to find this page
> >>> http://ant.apache.org/nightlies.html which lists the Ant/Ivy jobs.
> >>> Turns out we also have Teamcity builds for Ivy and they have been
> >>> failing since we moved to Java 1.7[1].
>
> Then I'd suggest migrating them to our
Doc's mentioning 'how to document' must be updated.
I found http://ant.apache.org/ivy/write-doc.html Some more?
Jan
> -Ursprüngliche Nachricht-
> Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
> Gesendet: Montag, 19. Juni 2017 04:52
> An: Ant Developers List
> Betreff: Ivy - we have
The Project Management Committee (PMC) for Apache Ant has invited Jaikiran
Pai to become a committer and we are pleased to announce that he has
accepted.
Being a committer enables easier contribution to the project since there is
no need to go via the patch submission process. This should
> -Ursprüngliche Nachricht-
> Von: Stefan Bodewig [mailto:bode...@apache.org]
> Gesendet: Mittwoch, 14. Juni 2017 09:17
> An: dev@ant.apache.org
> Betreff: Re: [VOTE] Release Compress Antlib 1.5 based on RC3
>
> On 2017-06-13, Jan Matèrne (jhm) wrote:
>
> >&g
> Should we include the PGP [e.g. 1] signature in the future?
Answer myself: should be only on ASF server, so people could trust that ;)
Maybe place a note (next time) how to check that (do we have a build snippet
for that?)
Jan
+1
Should we include the PGP [e.g. 1] signature in the future?
Jan
[1]
https://dist.apache.org/repos/dist/dev/ant/antlibs/compress/binaries/apache-
ant-compress-1.5-bin.zip.asc
> -Ursprüngliche Nachricht-
> Von: Stefan Bodewig [mailto:bode...@apache.org]
> Gesendet: Samstag, 10. Juni
+1
Jan
> -Ursprüngliche Nachricht-
> Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com]
> Gesendet: Dienstag, 6. Juni 2017 10:47
> An: Ant Developers List; Maarten Coene
> Betreff: Re: [VOTE] Release Compress Antlib 1.5 based on RC2
>
> +1 FWIW
>
> Gintas
>
> 2017-06-06 9:13
Some years ago there were a discussion about having ant-contrib a part of Ant.
Result was that it wasn't possible due IP (and therefore legal) reasons.
Having a look at the tasklist [1] there are some I would use:
* antcallback: maybe enhance
* antfetch: maybe (same base idea as antcallback)
*
https://github.com/apache/ant-ivy/pull/41
I found a comment in hibgraph.svg: "Helvetica is a registered trademark
of Linotype AG".
I am not sure about using that in an Apache project ...
I'll forward this to the dev llist. Maybe to legal@a.o later ...
Does someone know if we
we don’t run these tutorials build daily, it wasn’t noticed
> this far. It looks like this might have been introduced by some of our
> recent changes. I’ll take a look to fix it today.
>
> -Jaikiran
> On 03-Jun-2017, at 1:28 AM, Jan Matèrne (jhm) <apa...@materne.de>
>
> Would it be feasible to have a Jenkins daily job (runs once at a
> schedule) for Ivy which publishes the complete binary zip/tar.gz of Ivy
> nightly snapshots? I know we have a daily job currently here[1] which
> generates a jar as the artifact output of the job. Maybe this job
> itself can be
n *and* enhance the code of this task to explicit fail with
> a proper error when it can’t determine a common base directory.
> >
>
> Sounds good to me.
>
> Nicolas
>
>
> > -Jaikiran
> > On 02-Jun-2017, at 2:55 PM, Nicolas Lalevée
> <nicolas.l
>From a naive user point of view, it doesnt matter (to me) if I use
ivy:chachefileset or ivy:resources.
I want to specify the dependency and have a 'thing' which contains all required
jars, so I could
use external tasks/antlibs.
Ant itself moved from fileset to resource collection some years ago
The attachment didnt come thru.
I think EZMLM is configured not to send attachments ;)
Please open a JIRA ticket or a PR and we can discuss.
Jan
Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com]
Gesendet: Freitag, 2. Juni 2017 06:46
An: Ant Developers List
Betreff: Re:
I changed the Ivy build jobs to use Java7 instead of Java6.
Jan
[RESULT] [VOTE] Increase minimum Java version for Ivy to Java7
Here is the result of the vote to increase the minimum Java
version from current (Ivy-2.4.0) Java5 to Java 7 (Ivy-2.5.0):
+1:
Jan (binding)
Jaikiran (non-binding)
Gintautas (non-binding)
Nicolas (binding)
Dominique
Sounds like I would do ;)
I'll merge the PR locally and insert the delegates.
Open is
"src/java/org/apache/ivy/osgi/util/Version.java:
the constructor removes the (IMO unneccessary) ParseException.
But because it is a checked Exception we break BC."
Thanks, but I already have it done ;)
But one point is open:
src/java/org/apache/ivy/osgi/util/Version.java: the constructor removes the
(IMO unneccessary) ParseException. But because it is a checked Exception we
break BC.
Jan
> -Ursprüngliche Nachricht-
> Von: Gintautas Grigelionis
The task is having a code coverage.
The chosen tool should:
- do that ;)
- be free for OSS
- maintained
- useable by the project community (we have to use that ;)
- runnable in a CI environment
If a chosen tool (EMMA) does its job, you dont have to change this until
you'll get problems not to
Nope, haven't read that.
My first contact to a build is always executing the build without any
parameters. ;)
I'll have a look, thanks.
Jan
> -Ursprüngliche Nachricht-
> Von: Nicolas Lalevée [mailto:nicolas.lale...@hibnet.org]
> Gesendet: Freitag, 26. Mai 2017 17:21
> An: Ant
+1 for asciidoc.
Using xooki means using a tool only few people know ...
Jan
> -Ursprüngliche Nachricht-
> Von: J Pai [mailto:jai.forums2...@gmail.com]
> Gesendet: Donnerstag, 25. Mai 2017 14:03
> An: Ant Developers List
> Betreff: Re: Ivy website - fixing a Quickstart documentation live
The whole site is in svn and a server process (svnpubsub i think) is getting
the 'publish' files and pushing them to the webserver which brings them online.
We havent thought about a migrating that to git in the last few years ;)
If these files are really required, I could upload them.
Jan
git.GitException
> : Command "git checkout -f c1765c71ba4394597409de790bf4529ff97e866e"
> returned status code 128:
> stdout:
> stderr: fatal: reference is not a tree:
> c1765c71ba4394597409de790bf4529ff97e866e
>
> at
> org.jenkinsci.plugins.gitclient.CliGitA
I updated the job config and checked with
https://github.com/apache/ant-ivyde/pull/5.
IvyDE-GitHub-Integration should (really) work now.
Jan
> -Ursprüngliche Nachricht-
> Von: Jan Matèrne (jhm) [mailto:apa...@materne.de]
> Gesendet: Dienstag, 23. Mai 2017 15:57
> An: 'An
I did a quick check - I've forgotten to change two more checkboxes in the
job configuration.
Have it done now.
Sorry
Jan
> -Ursprüngliche Nachricht-
> Von: jaikiran [mailto:g...@git.apache.org]
> Gesendet: Dienstag, 23. Mai 2017 16:09
> An: dev@ant.apache.org
> Betreff: [GitHub]
E
>
> For some reason, this PR https://github.com/apache/ant-ivyde/pull/2
> hasn’t yet triggered that IvyDE-Github job
>
> -Jaikiran
> On 23-May-2017, at 12:54 AM, Jan Matèrne (jhm) <apa...@materne.de>
> wrote:
>
> I changed the buildjobs for IvyDE + IvyDE-Gi
I changed the buildjobs for IvyDE + IvyDE-Github to use Java7(latest).
But I prefer to use the lowest Java version we have defined as minimum. ;)
Jan
> -Ursprüngliche Nachricht-
> Von: J Pai [mailto:jai.forums2...@gmail.com]
> Gesendet: Montag, 22. Mai 2017 15:09
> An: Ant Developers
> > On a related note, while we are at this - does Apache infra allow the
> jobs to be run against Windows OS Jenkins agents as well? There are a
> few issues specifically reported against Windows OS and having the job
> run against linux and Windows OS should give a decent coverage for the
>
I'll try setting up the PreCommit-Job as Matrix job with Linux/Window.
Jan
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
I would favour 1.7 as it's the newest before the major update to Java8.
Having a 1.7 in the target environment should not been so restrictive ...
Jan
> -Ursprüngliche Nachricht-
> Von: Paul King [mailto:pa...@asert.com.au]
> Gesendet: Donnerstag, 18. Mai 2017 11:27
> An: Ant Developers
Ok, thanks.
Jan
> -Ursprüngliche Nachricht-
> Von: Nicolas Lalevée [mailto:nicolas.lale...@hibnet.org]
> Gesendet: Mittwoch, 17. Mai 2017 15:37
> An: dev@ant.apache.org
> Betreff: Re: [jira] [Resolved] (IVY-1520) Have makepom task take
> description from ivy-module > info > description
ich had
> succeeded had run on https://builds.apache.org/computer/qnode3/. Maybe
> all nodes are not equal and perhaps this job needs to be
> assigned/categorized to certain node groups?
>
> -Jaikiran
> On 17-May-2017, at 4:03 PM, Jan Matèrne (jhm) <apa...@materne.de>
> wrote:
&g
etup :)
>
> -Jaikiran
>
>
> On 17-May-2017, at 2:07 PM, J Pai <jai.forums2...@gmail.com> wrote:
>
> Doesn’t look like it got triggered in Jenkins.
>
> -Jaikiran
> On 17-May-2017, at 1:49 PM, Jan Matèrne (jhm) <apa...@materne.de>
> wrote:
>
> &
> I read the wiki page https://wiki.apache.org/general/PreCommitBuilds,
> the Kafka issue https://issues.apache.org/jira/browse/KAFKA-1856 and
> had a look at some other PreCommit-jobs.
> For me this works like that:
> 1. The PreCommit-Admin job checks regularly on for new patches in Jira.
> 2. It
> On the ICLA front - I already have contributed and continue to
> contribute to some other Apache projects (these days mostly via
> github). Do I still have to sign the ICLA?
The ICLA is for the ASF - so you don't have to sign a new one if you already
have submitted one.
> Is there a way to
Hello community
the Ant PMC hasn't been able to keep up with bugs reported for Ivy and IvyDE
for a while now. The number of active committers with the required knowledge
of the code base is getting smaller and we are having a hard time evaluating
patches.
We'd like to revive Ivy and IvyDE, but
It seems to be a REST interface for an Ivy repository.
Start the webapp, configure Ivy according to the repo layout and ready to use.
Looks nice.
But it's written in Groovy (I am not against Groovy, but I am not sure if here
is knowledge to maintain that).
Jan
> -Ursprüngliche
1 - 100 of 604 matches
Mail list logo
