[GitHub] ant-ivy pull request #28: DontMerge-testing-Github-integration

[janmaterne]

GitHub user janmaterne opened a pull request:

https://github.com/apache/ant-ivy/pull/28

DontMerge-testing-Github-integration



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/janmaterne/ant-ivy patch-3

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ant-ivy/pull/28.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #28


commit 9d1ed4d981f3cc277fd4ba320b2939a56a897ff5
Author: janmaterne 
Date:   2017-05-24T09:31:25Z

Update README




---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[GitHub] ant-ivy pull request #28: DontMerge-testing-Github-integration

[janmaterne]

Github user janmaterne closed the pull request at:

https://github.com/apache/ant-ivy/pull/28


---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[GitHub] ant-ivy pull request #29: DontMerge-testing-Github-integration2

[janmaterne]

Github user janmaterne closed the pull request at:

https://github.com/apache/ant-ivy/pull/29


---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[GitHub] ant-ivy issue #29: DontMerge-testing-Github-integration2

[janmaterne]

Github user janmaterne commented on the issue:

https://github.com/apache/ant-ivy/pull/29
  
retest this please


---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

AW: Ivy - Buildjobs/PreCommit

[jhm]

Not sure about this expertise because my sources were old, but I think the 
github-plugin does not support matrix jobs.
https://github.com/KostyaSha/github-integration-plugin/issues/53

Maybe a newer plugin version would do, but I could not see the version stamp.
I'll ask on builds@a.o for help.

For the meanwhile I deactivated the matrix-PR-job and reactivated the 'old' 
plain-PR-job.

If we can't get matrix support we should be to create our own 'matrix' by 
copying that job and sticking to certain configurations.
While a matrix would scale this approach won't. So we should define only 2-4 
most interesting configs like
- Java7@Unix
- Java7@Windows
- Java8@Unix


Jan

> -Ursprüngliche Nachricht-
> Von: J Pai [mailto:jai.forums2...@gmail.com]
> Gesendet: Montag, 22. Mai 2017 14:45
> An: Ant Developers List
> Betreff: Re: Ivy - Buildjobs/PreCommit
> 
> It looks like there might be some issue with the matrix job(s)
> https://builds.apache.org/job/Ivy-GithubPR-Matrix/2/console
> 
> From what I understand of that log, it seems like the parent matrix job
> (the one above) is correctly checking out the commit from the submitted
> PR:
> 
>  > Checking out Revision c1765c71ba4394597409de790bf4529ff97e866e
> (master)  > git config core.sparsecheckout # timeout=10  > git checkout
> -f c1765c71ba4394597409de790bf4529ff97e866e
>  > git rev-parse origin/master^{commit} # timeout=10  > git rev-list
> 239bc0b04a95d6c0f82e59c513de36d68c033c6a # timeout=10
> 
> However, it then hands off the job execution to individual
> Windows/Linux jobs and those jobs https://builds.apache.org/job/Ivy-
> GithubPR-Matrix/jdk=JDK%201.7%20(latest),os=ubuntu/2/console don’t seem
> to be able to checkout the commit(s) from the PR and fail with error
> like:
> 
> > Fetching upstream changes from https://github.com/apache/ant-ivy/
> 
>  > git --version # timeout=10
>  > git fetch --tags --progress
> https://github.com/apache/ant-ivy/
>  +refs/heads/*:refs/remotes/origin/*
> Checking out Revision c1765c71ba4394597409de790bf4529ff97e866e (master)
> > git config core.sparsecheckout # timeout=10  > git checkout -f
> c1765c71ba4394597409de790bf4529ff97e866e
> FATAL: Could not checkout c1765c71ba4394597409de790bf4529ff97e866e
> 
> hudson.plugins.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.CliGitAPIImpl.launchCommandIn(CliGitAPI
> Impl.java:1866)
> 
> 
> -Jaikiran
> 
> On 22-May-2017, at 12:25 PM, Jan Matèrne (jhm) 
> wrote:
> 
> >> 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
> > upstream code.
> >
> > In Jenkins there is the concept of « Matrix » job.
> > Here is the ones for Ant:
> > https://builds.apache.org/view/A/view/Ant/job/Ant-Build-Matrix-1.9.x-
> > Windows/  > Matrix-1.9.x-Windows/>
> > https://builds.apache.org/view/A/view/Ant/job/Ant-Build-Matrix-1.9.x-
> > Linux/
> >  > 1.9.x-Linux/>
> > AFAIR, it used to be able to do on several different OS. I don’t know
> > why they are split.
> >
> > And I don’t know if it is possible to do it while pulling a PR from
> > github.
> 
> 
> New buildjob "Ivy-GithubPR-Matrix". I deactivated the old (so we could
> easily switch back).
> https://builds.apache.org/view/A/view/Ant/job/Ivy-GithubPR-Matrix/
> Basically a copy of the old job:
> * discard old build jobs (keep 10)
> * git merge support: fail the build if push fails
> * github project: git://github.com/apache/ant-ivy.git
> * git
>  -- repository: git://github.com/apache/ant-ivy.git
>  -- branches: */master (= default)
>  -- clean before checkout
>  -- recursively update submodules
>  -- build commits submitted for validated merge (= PR support)
> * start build: build pull request to the repository (= PR support)
> * configuration matrix
>  -- JDK: JDK 1.7 (latest), JDK 1.8 (latest), JDK 9 b156 with jigsaw
>  -- os: label expression = ["ubuntu", "Windows"]
> * abort the build if it's stuck: absolute 20 minutes
> * Lock: Ant
> * build
>  -- ant(standard): clean coverage-report
> * publish junit: build/test-report/**
> 
> 
> Jan
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional
> commands, e-mail: dev-h...@ant.apache.org
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional
> commands, e-mail: dev-h...@ant.apache.org

[GitHub] ant-ivyde issue #4: Update the year in copyright messages

[jaikiran]

Github user jaikiran commented on the issue:

https://github.com/apache/ant-ivyde/pull/4
  
Thank you!


---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[GitHub] ant-ivy pull request #29: DontMerge-testing-Github-integration2

[janmaterne]

Github user janmaterne closed the pull request at:

https://github.com/apache/ant-ivy/pull/29


---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[GitHub] ant-ivy pull request #29: DontMerge-testing-Github-integration2

[janmaterne]

GitHub user janmaterne reopened a pull request:

https://github.com/apache/ant-ivy/pull/29

DontMerge-testing-Github-integration2



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/janmaterne/ant-ivy patch-4

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ant-ivy/pull/29.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #29


commit 1461defef7163a3774ca5a47d698e8635902d8ba
Author: janmaterne 
Date:   2017-05-24T10:20:01Z

Update README




---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[GitHub] ant-ivy pull request #29: DontMerge-testing-Github-integration2

[janmaterne]

GitHub user janmaterne opened a pull request:

https://github.com/apache/ant-ivy/pull/29

DontMerge-testing-Github-integration2



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/janmaterne/ant-ivy patch-4

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ant-ivy/pull/29.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #29


commit 1461defef7163a3774ca5a47d698e8635902d8ba
Author: janmaterne 
Date:   2017-05-24T10:20:01Z

Update README




---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy - Buildjobs/PreCommit

[Nicolas Lalevée]

> Le 24 mai 2017 à 13:13, Jan Matèrne (jhm)  a écrit :
> 
> Not sure about this expertise because my sources were old, but I think the 
> github-plugin does not support matrix jobs.
> https://github.com/KostyaSha/github-integration-plugin/issues/53
> 
> Maybe a newer plugin version would do, but I could not see the version stamp.
> I'll ask on builds@a.o for help.
> 
> For the meanwhile I deactivated the matrix-PR-job and reactivated the 'old' 
> plain-PR-job.
> 
> If we can't get matrix support we should be to create our own 'matrix' by 
> copying that job and sticking to certain configurations.
> While a matrix would scale this approach won't. So we should define only 2-4 
> most interesting configs like
> - Java7@Unix
> - Java7@Windows
> - Java8@Unix

I think we can even stick to only two configs. Testing on two different OS is 
the real pain and I don’t remember having big issues with jvm versions.

We could even for now stick to Windows if most committers are on Unix machines. 
At least I am.

And in the end we still have the more exhaustive matrix build which runs after 
the commit being merged into the asf repo.

Nicolas

> 
> 
> Jan
> 
>> -Ursprüngliche Nachricht-
>> Von: J Pai [mailto:jai.forums2...@gmail.com]
>> Gesendet: Montag, 22. Mai 2017 14:45
>> An: Ant Developers List
>> Betreff: Re: Ivy - Buildjobs/PreCommit
>> 
>> It looks like there might be some issue with the matrix job(s)
>> https://builds.apache.org/job/Ivy-GithubPR-Matrix/2/console
>> 
>> From what I understand of that log, it seems like the parent matrix job
>> (the one above) is correctly checking out the commit from the submitted
>> PR:
>> 
>>> Checking out Revision c1765c71ba4394597409de790bf4529ff97e866e
>> (master)  > git config core.sparsecheckout # timeout=10  > git checkout
>> -f c1765c71ba4394597409de790bf4529ff97e866e
>>> git rev-parse origin/master^{commit} # timeout=10  > git rev-list
>> 239bc0b04a95d6c0f82e59c513de36d68c033c6a # timeout=10
>> 
>> However, it then hands off the job execution to individual
>> Windows/Linux jobs and those jobs https://builds.apache.org/job/Ivy-
>> GithubPR-Matrix/jdk=JDK%201.7%20(latest),os=ubuntu/2/console don’t seem
>> to be able to checkout the commit(s) from the PR and fail with error
>> like:
>> 
>>> Fetching upstream changes from https://github.com/apache/ant-ivy/
>> 
>>> git --version # timeout=10
>>> git fetch --tags --progress
>> https://github.com/apache/ant-ivy/
>> +refs/heads/*:refs/remotes/origin/*
>> Checking out Revision c1765c71ba4394597409de790bf4529ff97e866e (master)
>>> git config core.sparsecheckout # timeout=10  > git checkout -f
>> c1765c71ba4394597409de790bf4529ff97e866e
>> FATAL: Could not checkout c1765c71ba4394597409de790bf4529ff97e866e
>> 
>> hudson.plugins.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.CliGitAPIImpl.launchCommandIn(CliGitAPI
>> Impl.java:1866)
>> 
>> 
>> -Jaikiran
>> 
>> On 22-May-2017, at 12:25 PM, Jan Matèrne (jhm) 
>> wrote:
>> 
 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
>>> upstream code.
>>> 
>>> In Jenkins there is the concept of « Matrix » job.
>>> Here is the ones for Ant:
>>> https://builds.apache.org/view/A/view/Ant/job/Ant-Build-Matrix-1.9.x-
>>> Windows/ >> Matrix-1.9.x-Windows/>
>>> https://builds.apache.org/view/A/view/Ant/job/Ant-Build-Matrix-1.9.x-
>>> Linux/
>>> >> 1.9.x-Linux/>
>>> AFAIR, it used to be able to do on several different OS. I don’t know
>>> why they are split.
>>> 
>>> And I don’t know if it is possible to do it while pulling a PR from
>>> github.
>> 
>> 
>> New buildjob "Ivy-GithubPR-Matrix". I deactivated the old (so we could
>> easily switch back).
>> https://builds.apache.org/view/A/view/Ant/job/Ivy-GithubPR-Matrix/
>> Basically a copy of the old job:
>> * discard old build jobs (keep 10)
>> * git merge support: fail the build if push fails
>> * github project: git://github.com/apache/ant-ivy.git
>> * git
>> -- repository: git://github.com/apache/ant-ivy.git
>> -- branches: */master (= default)
>> -- clean before checkout
>> -- recursively update submodules
>> -- build commits submitted for validated merge (= PR support)
>> * start build: build pull request to the repository (= PR support)
>> * configuration matrix
>> -- JDK: JDK 1.7 (latest), JDK 1.8 (latest), JDK 9 b156 with jigsaw
>> -- os: label expression = ["ubuntu", "Windows"]
>> * abort the build if it's 

[GitHub] ant-ivy pull request #27: Fix IVY-1540

[jaikiran]

Github user jaikiran closed the pull request at:

https://github.com/apache/ant-ivy/pull/27


---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[GitHub] ant-ivy issue #27: Fix IVY-1540

[jaikiran]

Github user jaikiran commented on the issue:

https://github.com/apache/ant-ivy/pull/27
  
retest this please


---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[GitHub] ant-ivy pull request #27: Fix IVY-1540

[jaikiran]

GitHub user jaikiran reopened a pull request:

https://github.com/apache/ant-ivy/pull/27

Fix IVY-1540

The commit here fixes the issue reported in 
https://issues.apache.org/jira/browse/IVY-1540. The dependency tree task now 
takes into account any potential circular dependencies that could result into a 
indefinite recursive calls.

This also includes a test case to verify such a use case.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jaikiran/ant-ivy ivy-1540

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ant-ivy/pull/27.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #27


commit 6cb32bd33e0e1d1758a3ed1d50df03b65032d9ac
Author: Jaikiran Pai 
Date:   2017-05-23T08:15:39Z

IVY-1540 Fix infinite loop in dependencytree, caused to due circular 
dependencies (coming in via Maven module descriptors)




---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[GitHub] ant-ivy issue #22: Fix transient test failures

[nlalevee]

Github user nlalevee commented on the issue:

https://github.com/apache/ant-ivy/pull/22
  
after many runs on my machine, I think I have found the actual issue. If 
testRemoveDuplicates is run after testRemoveDuplicates2, then it fails. It 
seems due to the fact that WarnCircularDependencyStrategy is a singleton and 
that circularDependencies in AbstractLogCircularDependencyStrategy is thus not 
reinitialized.
Not sure yet what the proper fix should be.


---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[GitHub] ant-ivy pull request #30: Fix transient test failures

[jaikiran]

GitHub user jaikiran opened a pull request:

https://github.com/apache/ant-ivy/pull/30

Fix transient test failures

The commit here fixes the transient test failures that we keep seeing in 
`WarnCircularDependencyStrategyTest`. More details about the fix are in this 
previous PR https://github.com/apache/ant-ivy/pull/22, but the real fix here is 
that we use a proper fresh `IvyContext` for each test method instead of 
unintentionally using the same one across test methods.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jaikiran/ant-ivy logger-test-fix

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ant-ivy/pull/30.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #30


commit da69323b29fe8e373364b9399bc67523dcf2af62
Author: Jaikiran Pai 
Date:   2017-05-20T03:43:17Z

Fix transient test failures - Don't share/update the MockMessageLogger 
between test methods




---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[GitHub] ant-ivy issue #22: Fix transient test failures

[jaikiran]

Github user jaikiran commented on the issue:

https://github.com/apache/ant-ivy/pull/22
  
That's a good find. Looking at that testcase now again, with this 
additional detail that you noted, I think the problem here is that the 
`AbstractLogCircularDependencyStrategy` ends up using a `IvyContext` which has 
been populated with a resolve id by that `testRemoveDuplicate2` test method. 
Effectively, it thinks that it has already made a note of that circular 
dependency and doesn't go ahead and add it or log it. 

I think the way to deal with this is to push/pop the relevant `IvyContext` 
for these test methods without each of them interfering with each other. I 
can't seem to reopen this PR with the updated testcase, so I'll open a separate 
PR with the potential fix (plus other few cleanup that I did in those tests 
previously). Let's see if that solves this issue.


---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Ivy website - fixing a Quickstart documentation live

[J Pai]

What would be the process of having the live docs of Ivy project updated to 
fix/update an issue in the documentation[1]? 

The quickstart documentation refers to certain log files that get 
auto-generated during the doc build process. It looks like those log files 
weren’t uploaded and are resulting in a blank text area showing up. I can run 
the doc generation target locally (on 2.4.0 tag) and have someone upload those 
files and see if shows up fine.

[1] https://issues.apache.org/jira/browse/IVY-1542

-Jaikiran
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy website - fixing a Quickstart documentation live

[Gintautas Grigelionis]

Is the documentation still in SVN? IVY-1542 is about site/sources/style
which is shared by Ivy and IvyDE. Are there any plans about migrating this
to Git and separating the source repo from publication repo?

Gintas

2017-05-25 6:12 GMT+02:00 J Pai :

> What would be the process of having the live docs of Ivy project updated
> to fix/update an issue in the documentation[1]?
>
> The quickstart documentation refers to certain log files that get
> auto-generated during the doc build process. It looks like those log files
> weren’t uploaded and are resulting in a blank text area showing up. I can
> run the doc generation target locally (on 2.4.0 tag) and have someone
> upload those files and see if shows up fine.
>
> [1] https://issues.apache.org/jira/browse/IVY-1542
>
> -Jaikiran
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

[GitHub] ant-ivyde pull request #5: DontMerge-Test-Github-Integration

[janmaterne]

GitHub user janmaterne opened a pull request:

https://github.com/apache/ant-ivyde/pull/5

DontMerge-Test-Github-Integration



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/janmaterne/ant-ivyde patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ant-ivyde/pull/5.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #5


commit 9a4c6b54eff134ad44904c206ed1928988e7b38a
Author: janmaterne 
Date:   2017-05-24T06:06:36Z

Update README.txt




---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

AW: Buildjob: IvyDE

[jhm]

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: 'Ant Developers List'
> Betreff: AW: Buildjob: IvyDE
> 
> The Github-support was deactivated. (For an unknown reason) I
> reactivated that.
> Please try again.
> 
> Jan
> 
> > -Ursprüngliche Nachricht-
> > Von: J Pai [mailto:jai.forums2...@gmail.com]
> > Gesendet: Dienstag, 23. Mai 2017 12:20
> > An: Ant Developers List
> > Betreff: Re: Buildjob: IvyDE
> >
> > 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) 
> > wrote:
> >
> > 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 List
> > > Betreff: Re: Buildjob: IvyDE
> > >
> > > Is there a chance you could trigger this build to run using Java 7?
> > > I read up a few JIRA posts for the INFRA project in
> > > issues.apache.org and they seem to indicate that this probably will
> > > work fine with builds that use Java 7. I’m not 100% sure though.
> > >
> > > -Jaikiran
> > > On 22-May-2017, at 6:30 PM, J Pai  wrote:
> > >
> > > That specific line in the build.xml[1] of the IvyDE project is
> > > trying to “get” the ivy.jar from a URL. In this case, it’s trying
> to
> > > fetch
> > it
> > > from:
> > >
> > >> [get] Getting:
> > >>
> > >
> >
> https://builds.apache.org/job/Ivy/lastSuccessfulBuild/artifact/build/a
> > >> rtifact/jars/ivy.jar
> > >
> > > Since it’s https backed, there’s a SSL handshake going on via this
> > > build process which is running on JRE 6 (upgrading to JRE 7 won’t
> > > solve the issue) and the builds.apache.org system while retrieving
> > the file.
> > > It looks like as noted here [2] that builds.apache.org is
> presenting
> > a
> > > certificate which JRE versions before JRE 8 don’t allow. The
> > > workaround presented in that FAQ is to switch the settings on the
> > > “server” which in this case would be builds.apache.org to use a
> > different cipher list.
> > >
> > > I’m not sure, if we will be allowed to do that and I’m curious how
> > > other builds (not necessary Ivy project builds) that need to fetch
> > > something from builds.apache.org via https and JRE <=7 get past
> this
> > > currently. Either way, I think this is something that we will have
> > > to ask the Apache infra team for their inputs.
> > >
> > >
> > > [1] https://github.com/apache/ant-ivyde/blob/master/build.xml#L277
> > > [2] http://httpd.apache.org/docs/current/ssl/ssl_faq.html#javadh
> > >
> > >
> > > -Jaikiran
> > > On 22-May-2017, at 2:04 PM, Jan Matèrne  wrote:
> > >
> > > I copied the IvyDE buildjob to have github support here.
> > >
> > > https://builds.apache.org/view/A/view/Ant/job/IvyDE-GithubPR/
> > >
> > >
> > >
> > > I changed IvyDE and IvyDE to not use "Ant latest" instead "Ant
> > 1.9.9",
> > > so it will work on Java<8.
> > >
> > >
> > >
> > > I started IvyDE and it gives me an error I could not interpret:
> > >
> > >
> https://builds.apache.org/view/A/view/Ant/job/IvyDE/lastBuild/consol
> > > e
> > >
> > >
> > >
> > > compute-ivy-bundle-version:
> > >  [mkdir] Created dir:
> > > /home/jenkins/jenkins-slave/workspace/IvyDE/work/ivy/jar
> > >[get] Getting:
> > >
> >
>  > > a
> > > rtifa
> > > ct/jars/ivy.jar>
> > >
> >
> https://builds.apache.org/job/Ivy/lastSuccessfulBuild/artifact/build/a
> > > r
> > > tifac
> > > t/jars/ivy.jar
> > >[get] To: /home/jenkins/jenkins-
> > > slave/workspace/IvyDE/work/ivy/ivy.jar
> > >[get] Error getting
> > >
> >
>  > > a
> > > rtifa
> > > ct/jars/ivy.jar>
> > >
> >
> https://builds.apache.org/job/Ivy/lastSuccessfulBuild/artifact/build/a
> > > r
> > > tifac
> > > t/jars/ivy.jar to
> > > /home/jenkins/jenkins-slave/workspace/IvyDE/work/ivy/ivy.jar
> > >
> > >
> > >
> > > BUILD FAILED
> > > /home/jenkins/jenkins-slave/workspace/IvyDE/build.xml:561: The
> > > following error occurred while executing this line:
> > > /home/jenkins/jenkins-slave/workspace/IvyDE/build.xml:277:
> > > javax.net.ssl.SSLException: java.lang.RuntimeException: Could not
> > > generate DH keypair
> > >  at
> > >
> com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:190)
> > >  at
> > >
> >
> com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:17
> > > 4
> > > 7)
> > >  at
> > >
> >
> 

[GitHub] ant-ivyde pull request #5: DontMerge-Test-Github-Integration

[janmaterne]

Github user janmaterne closed the pull request at:

https://github.com/apache/ant-ivyde/pull/5


---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[GitHub] ant-ivyde issue #5: DontMerge-Test-Github-Integration

[janmaterne]

Github user janmaterne commented on the issue:

https://github.com/apache/ant-ivyde/pull/5
  
Jenkins/Github-Integrationtest finished


---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[GitHub] ant-ivyde issue #4: Update the year in copyright messages

[janmaterne]

Github user janmaterne commented on the issue:

https://github.com/apache/ant-ivyde/pull/4
  
merged that to master


---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[GitHub] ant-ivyde pull request #4: Update the year in copyright messages

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ant-ivyde/pull/4


---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Versioning scheme in Ivy

[Gintautas Grigelionis]

I was thinking about the discussion which touched upon restricted
characters in version strings. While Ivy does not place any restrictions on
those strings, Ivy does support versions ranges as specified by OSGi. So,
what happens if version range is used as a version string?

Gintas

Re: Versioning scheme in Ivy

[Gintautas Grigelionis]

Sorry, I meant to ask what may happen if special characters from range
specification are used randomly in a version string?

Gintas

2017-05-24 10:15 GMT+02:00 Gintautas Grigelionis :

> I was thinking about the discussion which touched upon restricted
> characters in version strings. While Ivy does not place any restrictions on
> those strings, Ivy does support versions ranges as specified by OSGi. So,
> what happens if version range is used as a version string?
>
> Gintas
>

[GitHub] ant-ivy issue #30: Fix transient test failures

[jaikiran]

Github user jaikiran commented on the issue:

https://github.com/apache/ant-ivy/pull/30
  
Jenkins seems to have picked up the disabled Matrix job for this run. I'll 
wait for that to get sorted out.


---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org