DO NOT REPLY [Bug 44009] - MailLogger failed to send e-mail
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=44009.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44009
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
Target Milestone|--- |1.7.1
--- Additional Comments From [EMAIL PROTECTED] 2007-12-03 02:23 ---
line 216 is the iterator below, at least in SVN_HEAD:
msg.addHeader(Date, getDate());
for (Iterator iter = headers.iterator(); iter.hasNext();) {
Header h = (Header) iter.next();
msg.addHeader(h.getName(), h.getValue());
}
An NPE could be triggered by headers==null. There's nothing in the class
initialiser to set up these headers; it relies on setHeaders() being called,
which presumably, it isnt in this case, or the vector is being set with a null
pointer)
I'll do two things
-always initialise the vector
-skip the iteration if the vector is null (in case someone assigns a null vector
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 44009] - MailLogger failed to send e-mail
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=44009.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44009
--- Additional Comments From [EMAIL PROTECTED] 2007-12-03 02:50 ---
i tried making the following change on my local machine
if(headers!=null){
for (Iterator iter = headers.iterator(); iter.hasNext();) {
Header h = (Header) iter.next();
msg.addHeader(h.getName(), h.getValue());
}
}
and got the following stacktrace:
MailLogger failed to send e-mail!
Problem while sending mime mail:
at org.apache.tools.ant.taskdefs.email.MimeMailer.send(MimeMailer.java:2
43)
at org.apache.tools.ant.listener.MailLogger.sendMimeMail(MailLogger.java
:271)
at org.apache.tools.ant.listener.MailLogger.buildFinished(MailLogger.jav
a:139)
at org.apache.tools.ant.Project.fireBuildFinished(Project.java:2008)
at org.apache.tools.ant.Main.runBuild(Main.java:718)
at org.apache.tools.ant.Main.startAnt(Main.java:199)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
Caused by: javax.mail.MessagingException: [EOF]
at com.sun.mail.smtp.SMTPTransport.issueCommand(SMTPTransport.java:1481)
at com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1
512)
at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:1054)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:634)
at javax.mail.Transport.send0(Transport.java:189)
at javax.mail.Transport.send(Transport.java:118)
at org.apache.tools.ant.taskdefs.email.MimeMailer.send(MimeMailer.java:2
41)
... 7 more
--- Nested Exception ---
javax.mail.MessagingException: [EOF]
at com.sun.mail.smtp.SMTPTransport.issueCommand(SMTPTransport.java:1481)
at com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:1
512)
at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:1054)
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:634)
at javax.mail.Transport.send0(Transport.java:189)
at javax.mail.Transport.send(Transport.java:118)
at org.apache.tools.ant.taskdefs.email.MimeMailer.send(MimeMailer.java:2
41)
at org.apache.tools.ant.listener.MailLogger.sendMimeMail(MailLogger.java
:271)
at org.apache.tools.ant.listener.MailLogger.buildFinished(MailLogger.jav
a:139)
at org.apache.tools.ant.Project.fireBuildFinished(Project.java:2008)
at org.apache.tools.ant.Main.runBuild(Main.java:718)
at org.apache.tools.ant.Main.startAnt(Main.java:199)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
svn commit: r600481 - in /ant/ivy/core/trunk: src/java/org/apache/ivy/plugins/parser/m2/ test/java/org/apache/ivy/core/resolve/ test/repositories/m2/org/relocated/test3/1.1/ test/repositories/m2/org/r
Author: gscokart
Date: Mon Dec 3 03:12:23 2007
New Revision: 600481
URL: http://svn.apache.org/viewvc?rev=600481view=rev
Log:
(IVY-586) don't stop the resolution if the module is relocated to an other
version of the same module. The complete fix requires to handle relocation in
the resolution algorithm. This version will continue the resolution taking
partially into account the relocation, and printing an error. Note that
conflict resolution doesn't take into account the relocation
Added:
ant/ivy/core/trunk/test/repositories/m2/org/relocated/test3/1.1/
ant/ivy/core/trunk/test/repositories/m2/org/relocated/test3/1.1/test3-1.1.pom
(with props)
ant/ivy/core/trunk/test/repositories/m2/org/relocated/testRelocationUser/
ant/ivy/core/trunk/test/repositories/m2/org/relocated/testRelocationUser/1.0/
ant/ivy/core/trunk/test/repositories/m2/org/relocated/testRelocationUser/1.0/testRelocationUser-1.0.pom
(with props)
ant/ivy/core/trunk/test/repositories/m2/org/relocated/testRelocationUser/1.1/
ant/ivy/core/trunk/test/repositories/m2/org/relocated/testRelocationUser/1.1/testRelocationUser-1.1.pom
(with props)
Modified:
ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/parser/m2/PomModuleDescriptorParser.java
ant/ivy/core/trunk/test/java/org/apache/ivy/core/resolve/ResolveTest.java
Modified:
ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/parser/m2/PomModuleDescriptorParser.java
URL:
http://svn.apache.org/viewvc/ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/parser/m2/PomModuleDescriptorParser.java?rev=600481r1=600480r2=600481view=diff
==
---
ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/parser/m2/PomModuleDescriptorParser.java
(original)
+++
ant/ivy/core/trunk/src/java/org/apache/ivy/plugins/parser/m2/PomModuleDescriptorParser.java
Mon Dec 3 03:12:23 2007
@@ -146,8 +146,6 @@
private String organisation;
-private String relocationOrganisation = null;
-
private String module;
private String revision;
@@ -170,6 +168,8 @@
private StringBuffer buffer = new StringBuffer();
+private String relocationOrganisation = null;
+
private String relocationModule;
private String relocationRevision;
@@ -262,8 +262,8 @@
project/dependencies/dependency.equals(context)) {
if (revision == null) {
// if the revision is null, see if we can get it from the
dependency management
-String key = DEPENDENCY_MANAGEMENT +
DEPENDENCY_MANAGEMENT_DELIMITER + organisation +
-DEPENDENCY_MANAGEMENT_DELIMITER + module;
+String key = DEPENDENCY_MANAGEMENT +
DEPENDENCY_MANAGEMENT_DELIMITER
++ organisation + DEPENDENCY_MANAGEMENT_DELIMITER +
module;
revision = (String) properties.get(key);
}
if (dd == null) {
@@ -329,27 +329,50 @@
organisation = null;
module = null;
} else if
(project/distributionManagement/relocation.equals(context)) {
-md.setModuleRevisionId(ModuleRevisionId
-.newInstance(organisation, module, revision));
-if (relocationOrganisation == null ) {
+if (relocationOrganisation == null) {
relocationOrganisation = organisation;
}
-if (relocationModule == null ) {
+if (relocationModule == null) {
relocationModule = module;
}
-if (relocationRevision == null ) {
+if (relocationRevision == null) {
relocationRevision = revision;
}
-dd = new DefaultDependencyDescriptor(md,
ModuleRevisionId.newInstance(
-relocationOrganisation, relocationModule,
relocationRevision), true, false, true);
-dd.addDependencyConfiguration(*, @);
-md.addDependency(dd);
-dd = null;
+ModuleRevisionId myModuleRev = ModuleRevisionId.newInstance(
+organisation, module, revision);
+ModuleRevisionId relocationeModuleRev =
ModuleRevisionId.newInstance(
+relocationOrganisation, relocationModule,
relocationRevision);
+md.setModuleRevisionId(myModuleRev);
+if (relocationOrganisation.equals(organisation)
+ relocationModule.equals(module)) {
+Message.error(Relocation to an other version number not
supported in ivy :
++ myModuleRev + relocated to + relocationModule
++ . Please update your dependency to directly use the
right
[jira] Assigned: (IVY-586) ivy doesn't handle relocation in pom.xml
[ https://issues.apache.org/jira/browse/IVY-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gilles Scokart reassigned IVY-586: -- Assignee: (was: Gilles Scokart) I have committed a change that allows to handle the case of xml-api (relocated to an other version of itself). In that that case, I pick-up the dependies of the relocation and I add them to the relocated pom. That means that we might still have problems to get the artefact. In case of relocation to an other group/module, the relocation is just added as a dependency. In both case, the complete solution should consider the relocated element as if it had never existed. But this requires changes in the resolution algorithm, and it also impose to check every evicted element to be sure it has not been relocated to something that wouldn't be evicted. So indeed, the complete implementaion should be reported to alter. ivy doesn't handle relocation in pom.xml Key: IVY-586 URL: https://issues.apache.org/jira/browse/IVY-586 Project: Ivy Issue Type: Bug Affects Versions: 2.0.0-alpha-1 Reporter: Gilles Scokart Priority: Critical Fix For: 2.0 See for example : http://repo1.maven.org/maven2/dbunit/dbunit/2.2/dbunit-2.2.pom ivy, ignore the relocation content, and try to donwload the jar from http://repo1.maven.org/maven2/dbunit/dbunit/2.2/ (which doesn't exist) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
svn commit: r600530 - /ant/core/trunk/docs/manual/CoreTypes/dirset.html
Author: jhm
Date: Mon Dec 3 05:36:43 2007
New Revision: 600530
URL: http://svn.apache.org/viewvc?rev=600530view=rev
Log:
Example as discussed on [EMAIL PROTECTED] Select marked directories
Modified:
ant/core/trunk/docs/manual/CoreTypes/dirset.html
Modified: ant/core/trunk/docs/manual/CoreTypes/dirset.html
URL:
http://svn.apache.org/viewvc/ant/core/trunk/docs/manual/CoreTypes/dirset.html?rev=600530r1=600529r2=600530view=diff
==
--- ant/core/trunk/docs/manual/CoreTypes/dirset.html (original)
+++ ant/core/trunk/docs/manual/CoreTypes/dirset.html Mon Dec 3 05:36:43 2007
@@ -92,6 +92,7 @@
/table
h4Examples/h4
+
blockquotepre
lt;dirset dir=quot;${build.dir}quot;gt;
lt;include name=quot;apps/**/classesquot;/gt;
@@ -101,6 +102,7 @@
pGroups all directories named codeclasses/code found under the
codeapps/code subdirectory of code${build.dir}/code, except those
that have the text codeTest/code in their name./p
+
blockquotepre
lt;dirset dir=quot;${build.dir}quot;gt;
lt;patternset id=quot;non.test.classesquot;gt;
@@ -112,6 +114,7 @@
pGroups the same directories as the above example, but also establishes
a PatternSet that can be referenced in other
codelt;dirsetgt;/code elements, rooted at a different directory./p
+
blockquotepre
lt;dirset dir=quot;${debug_build.dir}quot;gt;
lt;patternset refid=quot;non.test.classesquot;/gt;
@@ -120,6 +123,15 @@
pGroups all directories in directory code${debug_build.dir}/code,
using the same patterns as the above example./p
+blockquotepre
+lt;dirset id=quot;dirsetquot; dir=quot;${workingdir}quot;gt;
+ lt;present targetdir=quot;${workingdir}quot;gt;
+lt;mapper type=quot;globquot; from=quot;*quot;
to=quot;*/${markerfile}quot; /gt;
+ lt;/presentgt;
+lt;/dirsetgt;
+/pre/blockquote
+pSelects all directories somewhere under code${workingdir}/code
+which contain a code${markerfile}/code./p
/body
[jira] Created: (IVY-655) Ease performance auditing
Ease performance auditing -- Key: IVY-655 URL: https://issues.apache.org/jira/browse/IVY-655 Project: Ivy Issue Type: Improvement Reporter: Xavier Hanin Assignee: Xavier Hanin Ivy currently provides some performance metrics (size and time when downloading a file), but their location in the log make it difficult to use. On the other hand, the trigger mechanism can be used to track how things are performed, but is lacking basic performance information such as the download time. Improving the events triggered during the resolution process with more performance related metrics would help to investigate performance issues and improve Ivy setup. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[EMAIL PROTECTED]: Project dotnet-antlib-test (in module ant-antlibs) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project dotnet-antlib-test has an issue affecting its community integration. This issue affects 1 projects, and has been outstanding for 377 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - dotnet-antlib-test : Task and Type Libraries for Apache Ant Full details are available at: http://vmgump.apache.org/gump/public/ant-antlibs/dotnet-antlib-test/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed The following work was performed: http://vmgump.apache.org/gump/public/ant-antlibs/dotnet-antlib-test/gump_work/build_ant-antlibs_dotnet-antlib-test.html Work Name: build_ant-antlibs_dotnet-antlib-test (Type: Build) Work ended in a state of : Failed Elapsed: 35 secs Command Line: /usr/lib/jvm/java-1.5.0-sun/bin/java -Djava.awt.headless=true -Xbootclasspath/p:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dant-testutil.jar=/srv/gump/public/workspace/ant/build/lib/ant-testutil.jar test [Working Directory: /srv/gump/public/workspace/ant-antlibs/dotnet] CLASSPATH: /usr/lib/jvm/java-1.5.0-sun/lib/tools.jar:/srv/gump/public/workspace/ant-antlibs/dotnet/build/test-classes:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-trax.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant-antlibs/antunit/build/ant-antunit-03122007.jar:/srv/gump/public/workspace/ant-antlibs/dotnet/build/ant-dotnet-03122007.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis-ext.jar - [au:antunit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.05 sec [au:antunit] Target: test-passing took 0.013 sec [au:antunit] Build File: /srv/gump/public/workspace/ant-antlibs/dotnet/src/tests/antunit/dir with spaces/wsdl-test.xml [au:antunit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.935 sec [au:antunit] Target: testWSDL took 1.908 sec [au:antunit] Build File: /srv/gump/public/workspace/ant-antlibs/dotnet/src/tests/antunit/dotnetexec-test.xml [au:antunit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.86 sec [au:antunit] Target: testCSC took 0.752 sec [au:antunit] Build File: /srv/gump/public/workspace/ant-antlibs/dotnet/src/tests/antunit/nunit/nunit-test.xml [au:antunit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.276 sec [au:antunit] Target: test-passing took 0.004 sec [au:antunit] Target: test-failing took 0.002 sec [au:antunit] Target: test-failing-errorproperty took 0.183 sec [au:antunit] Target: test-failing-with-fail took 0.005 sec [au:antunit] Target: test-no-assembly took 0.007 sec [au:antunit] Build File: /srv/gump/public/workspace/ant-antlibs/dotnet/src/tests/antunit/old-core-test.xml [au:antunit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 5.437 sec [au:antunit] Target: testCSCintrinsicFileset took 0.748 sec [au:antunit] Target: testCSCresponseFile took 0.651 sec [au:antunit] Target: testILASM took 0.845 sec [au:antunit] Target: testCSCdll took 0.632 sec [au:antunit] Target: testILDASM took 0.728 sec [au:antunit] Target: testILDASM_empty took 0.052 sec [au:antunit] Target: testJsharp took 0.086 sec [au:antunit] Target: testCSCResources took 0.729 sec [au:antunit] Target: testCSC took 0.776 sec [au:antunit] Build File: /srv/gump/public/workspace/ant-antlibs/dotnet/src/tests/antunit/wsdl2dotnet-test.xml [au:antunit] Tests run: 15, Failures: 0, Errors: 0, Time elapsed: 4.039 sec [au:antunit] Target: testSchemaMustBeSet took 0.023 sec [au:antunit] Target: testLocalWsdlVB took 0.092 sec [au:antunit] Target: testInvalidExtraOps took 0.029 sec [au:antunit] Target: testSrcIsMissing took 0.042 sec [au:antunit] Target: testNoParams took 0.02 sec [au:antunit] Target: testBothSrc took 0.015 sec [au:antunit] Target: testSchemaFileMustHaveOneOptionOnly took 0.015 sec [au:antunit] Target: testLocalWsdl took 1.568 sec [au:antunit] Target: testSrcIsDir took 0.025 sec [au:antunit] Target: testLocalWsdlServerVB took 0.01 sec [au:antunit] Target: testLocalWsdlServer took 1.877 sec [au:antunit] Target: testNoSrc took 0.015 sec [au:antunit] Target:
[jira] Updated: (IVYDE-64) Simplify the resolve process
[
https://issues.apache.org/jira/browse/IVYDE-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Lalevée updated IVYDE-64:
-
Attachment: IVYDE-64-r600683.patch
So here is a new patch. So as discussed, the {{usePreviousResolveIfExist}}
check is kept. And there is still in the patch the eviction of parsing the
report if we already have the artifacts.
I think I have mostly made the code simpler to understand. The functionnalites
of the code are all here, even some error handling (parsing and IO exception
which is fallbacking to a complete resolve).
I also included in that patch a little part of the patch of IVYDE-43 : use the
IClasspathEntry more than the inner ClasspathItem class.
Then the patch may appear quite big. But I am not sure what the indentation
convention are here. I know there is a migration in progress (IVY-511), but the
convention doesn't specify if we should use spaces or tabs. I personnaly
prefers spaces, so I used them. Editing with eclipse, it did some strange mix,
but I tried to not make the patch appears as a complete diff.
I have tested this patch with some ivy-aware project, it works fine.
Simplify the resolve process
Key: IVYDE-64
URL: https://issues.apache.org/jira/browse/IVYDE-64
Project: IvyDE
Issue Type: Improvement
Components: classpath container
Affects Versions: 1.3.0
Environment: trunk r595956
Reporter: Nicolas Lalevée
Attachments: IVYDE-64-r595956.patch, IVYDE-64-r600683.patch
The current trunk, the resolve job is first checking manually if the artifact
has already been resolved. If not in cache, it let ivy resolve it. And
finally it parses the xml reports in the cache.
So first, as far as I have understood, the manual checking against the cache
is not needed, ivy already does it.
And then ivy produce in Java some resolve report that already contain every
needed information, there is no need to parse the reports in cache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (IVY-629) The chainedresolvers-project does not pick up the settings file
[ https://issues.apache.org/jira/browse/IVY-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maarten Coene resolved IVY-629. --- Resolution: Fixed Fix Version/s: 2.0.0-beta-1 Assignee: Xavier Hanin This has already been fixed by Xavier when reviewing the examples. The chainedresolvers-project does not pick up the settings file --- Key: IVY-629 URL: https://issues.apache.org/jira/browse/IVY-629 Project: Ivy Issue Type: Bug Affects Versions: 2.0.0-alpha-2 Reporter: Jacob Grydholt Jensen Assignee: Xavier Hanin Fix For: 2.0.0-beta-1 When I run the chainedresolvers-project example the ivysettings.xml file is not picked up. Instead the default ivysettings.xml file is picked up from the jar-file and the build fails. The output of the build: [EMAIL PROTECTED]:~/workspace/ivy/src/example/chained-resolvers/chainedresolvers-project$ ant -lib ../../../../build/artifact/ Buildfile: build.xml resolve: [ivy:retrieve] :: Ivy 2.0.0-beta1-local-20071020005610 - 20071020005610 :: http://incubator.apache.org/ivy/ :: [ivy:retrieve] No ivy:settings found for the default reference 'ivy.instance'. A default instance will be used [ivy:retrieve] no settings file found, using default... [ivy:retrieve] :: loading settings :: url = jar:file:/home/grydholt/workspace/ivy/src/example/chained-resolvers/chainedresolvers-project/../../../../build/artifact/ivy.jar!/org/apache/ivy/core/settings/ivysettings.xml [ivy:retrieve] :: resolving dependencies :: [ apache | chained-resolvers | [EMAIL PROTECTED] ] [ivy:retrieve] confs: [default] [ivy:retrieve] :: resolution report :: - | |modules|| artifacts | | conf | number| search|dwnlded|evicted|| number|dwnlded| - | default | 2 | 0 | 0 | 0 || 0 | 0 | - [ivy:retrieve] [ivy:retrieve] :: problems summary :: [ivy:retrieve] WARNINGS [ivy:retrieve] module not found: [ apache | commons-lang | 2.0 ] [ivy:retrieve] local: tried [ivy:retrieve] /home/grydholt/.ivy2/local/apache/commons-lang/2.0/ivys/ivy.xml [ivy:retrieve]-- artifact [ apache | commons-lang | 2.0 ]/commons-lang.jar[jar]: [ivy:retrieve] /home/grydholt/.ivy2/local/apache/commons-lang/2.0/jars/commons-lang.jar [ivy:retrieve] shared: tried [ivy:retrieve] /home/grydholt/.ivy2/shared/apache/commons-lang/2.0/ivys/ivy.xml [ivy:retrieve]-- artifact [ apache | commons-lang | 2.0 ]/commons-lang.jar[jar]: [ivy:retrieve] /home/grydholt/.ivy2/shared/apache/commons-lang/2.0/jars/commons-lang.jar [ivy:retrieve] public: tried [ivy:retrieve] http://repo1.maven.org/maven2/apache/commons-lang/2.0/commons-lang-2.0.pom [ivy:retrieve]-- artifact [ apache | commons-lang | 2.0 ]/commons-lang.jar[jar]: [ivy:retrieve] http://repo1.maven.org/maven2/apache/commons-lang/2.0/commons-lang-2.0.jar [ivy:retrieve] module not found: [ apache | test | 1.0 ] [ivy:retrieve] local: tried [ivy:retrieve]/home/grydholt/.ivy2/local/apache/test/1.0/ivys/ivy.xml [ivy:retrieve]-- artifact [ apache | test | 1.0 ]/test.jar[jar]: [ivy:retrieve]/home/grydholt/.ivy2/local/apache/test/1.0/jars/test.jar [ivy:retrieve] shared: tried [ivy:retrieve]/home/grydholt/.ivy2/shared/apache/test/1.0/ivys/ivy.xml [ivy:retrieve]-- artifact [ apache | test | 1.0 ]/test.jar[jar]: [ivy:retrieve]/home/grydholt/.ivy2/shared/apache/test/1.0/jars/test.jar [ivy:retrieve] public: tried [ivy:retrieve]http://repo1.maven.org/maven2/apache/test/1.0/test-1.0.pom [ivy:retrieve]-- artifact [ apache | test | 1.0 ]/test.jar[jar]: [ivy:retrieve]http://repo1.maven.org/maven2/apache/test/1.0/test-1.0.jar [ivy:retrieve] :: [ivy:retrieve] :: UNRESOLVED DEPENDENCIES :: [ivy:retrieve] :: [ivy:retrieve] :: [ apache | commons-lang | 2.0 ]: not found [ivy:retrieve] :: [ apache | test | 1.0 ]: not found [ivy:retrieve] :: [ivy:retrieve] [ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS BUILD FAILED /home/grydholt/workspace/ivy/src/example/chained-resolvers/chainedresolvers-project/build.xml:43: impossible to resolve dependencies: resolve failed - see output for details -- This message is automatically generated by JIRA. -
