Re: Ivy 2.0.0-rc1 PomModuleDescriptorWriter

2008-09-19 Thread Xavier Hanin 
On Fri, Sep 19, 2008 at 12:10 AM, Wardrip, Paul [EMAIL PROTECTED]wrote:

 I entered one about multiple artifacts and included the patch I've been
 using with beta2: https://issues.apache.org/jira/browse/IVY-770

 I tried to setup one of my projects so each artifact has a separate
 build.xml and ivy.xml, but a relative path of ../target was breaking
 ivy:retrieve/ when I used subant. Am I correct in assuming that
 https://issues.apache.org/jira/browse/IVY-232 will fix this?

Yes, it should, but you can try 2.0-rc1 attempt to see if it works. And note
that the workaround is pretty easy: use ${basedir}/../target.




 If I can setup this kind of build then I can work around the multi
 artifact issue (although it's just like needing a pom for each artifact
 in maven... yuck). The packaging issue would still force me to compile
 my own ivy.jar. I would rather use the release unmodified, I'm sure the
 management would like that too. ;)

Sure. But now we are in feature freeze mode for 2.0.x, so this improvement
will probably not be included before 2.1.

Xavier



 --pw

 -Original Message-
 From: Maarten Coene [mailto:[EMAIL PROTECTED]
 Sent: Thursday, September 18, 2008 4:56 PM
 To: Ant Developers List
 Subject: Re: Ivy 2.0.0-rc1 PomModuleDescriptorWriter

 Indeed, and an error (or warning) could be thrown if you Ivy module
 defines an artifact having a different name than the module name.
 I think there was a JIRA issue as well for supporting more than 1
 artifact...

 Maarten



 - Original Message 
 From: Xavier Hanin [EMAIL PROTECTED]
 To: Ant Developers List dev@ant.apache.org
 Sent: Thursday, September 18, 2008 10:49:40 PM
 Subject: Re: Ivy 2.0.0-rc1 PomModuleDescriptorWriter

 On Thu, Sep 18, 2008 at 10:12 PM, Wardrip, Paul
 [EMAIL PROTECTED]wrote:

  In PomModuleDescriptorWriter.java would it be possible to change hard
  coded jar value that is written for packaging to use the artifact
  extension? If I publish something that isn't a jar to a maven
  repository, ivy expects it to be a jar when I try to use it as a
  dependency of another project.
 
 private static void printModuleId(ModuleDescriptor md, PrintWriter
  out) {
 ModuleRevisionId mrid = md.getModuleRevisionId();
 out.println(  groupId + mrid.getOrganisation() +
  /groupId);
 out.println(  artifactId + mrid.getName() +
  /artifactId);
 out.println(  packagingjar/packaging);
 
  --  to --
 
 out.println(  packaging + artifacts[i].getExt() +
  /packaging);


 The only problem I see to implement it is that in Ivy you can have
 multiple artifacts, while in Maven you have only one (well, you can have
 more with qualifiers, but you have one main artifact). So the patch is
 not that easy, but it could be at least improved when only one artifact
 is published by the Ivy module.

 Xavier


 
  
  Paul Wardrip
  Software Engineer, OpenStream
  TANDBERG Television | Part of the Ericsson Group 4500 River Green
  Parkway | Duluth | GA 30096
  Mobile: 770-312-2852 | AIM: paulwardrip
  Email: [EMAIL PROTECTED] | www.tandbergtv.com
 
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
  commands, e-mail: [EMAIL PROTECTED]
 
 


 --
 Xavier Hanin - Independent Java Consultant BordeauxJUG co leader -
 http://www.bordeauxjug.org/ Blogger - http://xhab.blogspot.com/ Apache
 Ivy Creator - http://ant.apache.org/ivy/





 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-- 
Xavier Hanin - Independent Java Consultant
BordeauxJUG co leader - http://www.bordeauxjug.org/
Blogger - http://xhab.blogspot.com/
Apache Ivy Creator - http://ant.apache.org/ivy/

Ivy 2.0.0-rc1 PomModuleDescriptorWriter

2008-09-18 Thread Wardrip, Paul 
In PomModuleDescriptorWriter.java would it be possible to change hard
coded jar value that is written for packaging to use the artifact
extension? If I publish something that isn't a jar to a maven
repository, ivy expects it to be a jar when I try to use it as a
dependency of another project.

private static void printModuleId(ModuleDescriptor md, PrintWriter
out) {
ModuleRevisionId mrid = md.getModuleRevisionId();
out.println(  groupId + mrid.getOrganisation() +
/groupId);
out.println(  artifactId + mrid.getName() +
/artifactId);
out.println(  packagingjar/packaging);
 
--  to --
   
out.println(  packaging + artifacts[i].getExt() +
/packaging);


Paul Wardrip
Software Engineer, OpenStream
TANDBERG Television | Part of the Ericsson Group
4500 River Green Parkway | Duluth | GA 30096
Mobile: 770-312-2852 | AIM: paulwardrip
Email: [EMAIL PROTECTED] | www.tandbergtv.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ivy 2.0.0-rc1 PomModuleDescriptorWriter

2008-09-18 Thread Maarten Coene 
If you want this issue to be fixed, please do

- vote for https://issues.apache.org/jira/browse/IVY-736, or
- attach a patch to this issue, or
- attach a junit test to this issue, or
- do all of the things above :-)

Maarten



- Original Message 
From: Wardrip, Paul [EMAIL PROTECTED]
To: Ant Developers List dev@ant.apache.org
Sent: Thursday, September 18, 2008 10:12:16 PM
Subject: Ivy 2.0.0-rc1 PomModuleDescriptorWriter

In PomModuleDescriptorWriter.java would it be possible to change hard
coded jar value that is written for packaging to use the artifact
extension? If I publish something that isn't a jar to a maven
repository, ivy expects it to be a jar when I try to use it as a
dependency of another project.

private static void printModuleId(ModuleDescriptor md, PrintWriter
out) {
ModuleRevisionId mrid = md.getModuleRevisionId();
out.println(  groupId + mrid.getOrganisation() +
/groupId);
out.println(  artifactId + mrid.getName() +
/artifactId);
out.println(  packagingjar/packaging);

--to --
  
out.println(  packaging + artifacts[i].getExt() +
/packaging);


Paul Wardrip
Software Engineer, OpenStream
TANDBERG Television | Part of the Ericsson Group
4500 River Green Parkway | Duluth | GA 30096
Mobile: 770-312-2852 | AIM: paulwardrip
Email: [EMAIL PROTECTED] | www.tandbergtv.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Ivy 2.0.0-rc1 PomModuleDescriptorWriter

2008-09-18 Thread Xavier Hanin 
On Thu, Sep 18, 2008 at 10:12 PM, Wardrip, Paul [EMAIL PROTECTED]wrote:

 In PomModuleDescriptorWriter.java would it be possible to change hard
 coded jar value that is written for packaging to use the artifact
 extension? If I publish something that isn't a jar to a maven
 repository, ivy expects it to be a jar when I try to use it as a
 dependency of another project.

private static void printModuleId(ModuleDescriptor md, PrintWriter
 out) {
ModuleRevisionId mrid = md.getModuleRevisionId();
out.println(  groupId + mrid.getOrganisation() +
 /groupId);
out.println(  artifactId + mrid.getName() +
 /artifactId);
out.println(  packagingjar/packaging);

 --  to --

out.println(  packaging + artifacts[i].getExt() +
 /packaging);


The only problem I see to implement it is that in Ivy you can have multiple
artifacts, while in Maven you have only one (well, you can have more with
qualifiers, but you have one main artifact). So the patch is not that easy,
but it could be at least improved when only one artifact is published by the
Ivy module.

Xavier



 
 Paul Wardrip
 Software Engineer, OpenStream
 TANDBERG Television | Part of the Ericsson Group
 4500 River Green Parkway | Duluth | GA 30096
 Mobile: 770-312-2852 | AIM: paulwardrip
 Email: [EMAIL PROTECTED] | www.tandbergtv.com


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-- 
Xavier Hanin - Independent Java Consultant
BordeauxJUG co leader - http://www.bordeauxjug.org/
Blogger - http://xhab.blogspot.com/
Apache Ivy Creator - http://ant.apache.org/ivy/

Re: Ivy 2.0.0-rc1 PomModuleDescriptorWriter

2008-09-18 Thread Maarten Coene 
Indeed, and an error (or warning) could be thrown if you Ivy module defines an 
artifact having a different name than the module name.
I think there was a JIRA issue as well for supporting more than 1 artifact...

Maarten



- Original Message 
From: Xavier Hanin [EMAIL PROTECTED]
To: Ant Developers List dev@ant.apache.org
Sent: Thursday, September 18, 2008 10:49:40 PM
Subject: Re: Ivy 2.0.0-rc1 PomModuleDescriptorWriter

On Thu, Sep 18, 2008 at 10:12 PM, Wardrip, Paul [EMAIL PROTECTED]wrote:

 In PomModuleDescriptorWriter.java would it be possible to change hard
 coded jar value that is written for packaging to use the artifact
 extension? If I publish something that isn't a jar to a maven
 repository, ivy expects it to be a jar when I try to use it as a
 dependency of another project.

private static void printModuleId(ModuleDescriptor md, PrintWriter
 out) {
ModuleRevisionId mrid = md.getModuleRevisionId();
out.println(  groupId + mrid.getOrganisation() +
 /groupId);
out.println(  artifactId + mrid.getName() +
 /artifactId);
out.println(  packagingjar/packaging);

 --  to --

out.println(  packaging + artifacts[i].getExt() +
 /packaging);


The only problem I see to implement it is that in Ivy you can have multiple
artifacts, while in Maven you have only one (well, you can have more with
qualifiers, but you have one main artifact). So the patch is not that easy,
but it could be at least improved when only one artifact is published by the
Ivy module.

Xavier



 
 Paul Wardrip
 Software Engineer, OpenStream
 TANDBERG Television | Part of the Ericsson Group
 4500 River Green Parkway | Duluth | GA 30096
 Mobile: 770-312-2852 | AIM: paulwardrip
 Email: [EMAIL PROTECTED] | www.tandbergtv.com


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-- 
Xavier Hanin - Independent Java Consultant
BordeauxJUG co leader - http://www.bordeauxjug.org/
Blogger - http://xhab.blogspot.com/
Apache Ivy Creator - http://ant.apache.org/ivy/



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Ivy 2.0.0-rc1 PomModuleDescriptorWriter

2008-09-18 Thread Wardrip, Paul 
I entered one about multiple artifacts and included the patch I've been
using with beta2: https://issues.apache.org/jira/browse/IVY-770

I tried to setup one of my projects so each artifact has a separate
build.xml and ivy.xml, but a relative path of ../target was breaking
ivy:retrieve/ when I used subant. Am I correct in assuming that
https://issues.apache.org/jira/browse/IVY-232 will fix this? 

If I can setup this kind of build then I can work around the multi
artifact issue (although it's just like needing a pom for each artifact
in maven... yuck). The packaging issue would still force me to compile
my own ivy.jar. I would rather use the release unmodified, I'm sure the
management would like that too. ;) 

--pw  

-Original Message-
From: Maarten Coene [mailto:[EMAIL PROTECTED] 
Sent: Thursday, September 18, 2008 4:56 PM
To: Ant Developers List
Subject: Re: Ivy 2.0.0-rc1 PomModuleDescriptorWriter

Indeed, and an error (or warning) could be thrown if you Ivy module
defines an artifact having a different name than the module name.
I think there was a JIRA issue as well for supporting more than 1
artifact...

Maarten



- Original Message 
From: Xavier Hanin [EMAIL PROTECTED]
To: Ant Developers List dev@ant.apache.org
Sent: Thursday, September 18, 2008 10:49:40 PM
Subject: Re: Ivy 2.0.0-rc1 PomModuleDescriptorWriter

On Thu, Sep 18, 2008 at 10:12 PM, Wardrip, Paul
[EMAIL PROTECTED]wrote:

 In PomModuleDescriptorWriter.java would it be possible to change hard 
 coded jar value that is written for packaging to use the artifact 
 extension? If I publish something that isn't a jar to a maven 
 repository, ivy expects it to be a jar when I try to use it as a 
 dependency of another project.

private static void printModuleId(ModuleDescriptor md, PrintWriter
 out) {
ModuleRevisionId mrid = md.getModuleRevisionId();
out.println(  groupId + mrid.getOrganisation() + 
 /groupId);
out.println(  artifactId + mrid.getName() + 
 /artifactId);
out.println(  packagingjar/packaging);

 --  to --

out.println(  packaging + artifacts[i].getExt() + 
 /packaging);


The only problem I see to implement it is that in Ivy you can have
multiple artifacts, while in Maven you have only one (well, you can have
more with qualifiers, but you have one main artifact). So the patch is
not that easy, but it could be at least improved when only one artifact
is published by the Ivy module.

Xavier



 
 Paul Wardrip
 Software Engineer, OpenStream
 TANDBERG Television | Part of the Ericsson Group 4500 River Green 
 Parkway | Duluth | GA 30096
 Mobile: 770-312-2852 | AIM: paulwardrip
 Email: [EMAIL PROTECTED] | www.tandbergtv.com


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional 
 commands, e-mail: [EMAIL PROTECTED]




--
Xavier Hanin - Independent Java Consultant BordeauxJUG co leader -
http://www.bordeauxjug.org/ Blogger - http://xhab.blogspot.com/ Apache
Ivy Creator - http://ant.apache.org/ivy/



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]