not-working ivy.xml: (published only ivy.xml)

<ivy-module version="1.0">
   <info organisation="ivy-bug" module="test_proj" revision="1.0"/>

   <configurations>
       <conf name="compile" transitive="false"/>
       <conf name="runtime"/>
   </configurations>

   <publications>
       <artifact name="test_proj" type="jar" conf="compile; runtime"/>
   </publications>

</ivy-module>



Working ivy.xml (publishes also jar):

<ivy-module version="1.0">
   <info organisation="ivy-bug" module="test_proj" revision="1.0"/>

   <configurations>
       <conf name="compile" transitive="false"/>
       <conf name="runtime"/>
   </configurations>

   <publications>
       <artifact name="test_proj" type="jar" conf="compile, runtime"/>
   </publications>

</ivy-module>


Notice the ';' and ',' in publications/artifact/@conf.

Keep in mind that this is also confusing since where no conf mapping is used
in dependencies (i.e. no -> operator in conf attribute), the ',' and ';'
have the same meaning. I expected the same behavior in publications element.

-easyproglife


On 3/20/07, Xavier Hanin <[EMAIL PROTECTED]> wrote:

On 3/20/07, easyproglife <[EMAIL PROTECTED]> wrote:
>
> Well I have found!
>
> In publications tag, in artifact's conf attribute, I uses 2
> configurations.
> They were separated with ';'. I have changed it to ',' and it magically
> working again :-)
>
> I think it's a bug right? A really strange and nonsense bug...


It seems to be a bug, but could you provide your ivy file so that we can
have more details?

-easyproglife
>
> On 3/20/07, easyproglife <[EMAIL PROTECTED]> wrote:
> >
> > Hi.
> >
> > Any idea why ivy:publish just publishes ivy.xml but not the jar files?
> >
> > I have set of many projects with same common build.xml. For the other
> > projects it's working fine. For a specific project it doesn't. All
> > properties are same. ivy.publish.src.artifacts.pattern property is
also
> > pointing to the right location. JAR names are ok.
> >
> > What could go wrong? Any idea?
> >
> > Thanks
> > -easyproglife
> >
>

Reply via email to