Correct dependency for maven 2?

[Konstantin Priblouda]

Hi all,

Somehow I'm unable to download WSTX 4.0.0 from maven repository.

I'm using:
        <dependency>
           <groupId>org.codehaus.woodstox</groupId>
           <artifactId>wstx-asl</artifactId>
           <version>4.0.0</version>
       </dependency>  

But in the codehaus repo artifacts are named like:

http://repository.codehaus.org/org/codehaus/woodstox/wstx-lgpl/4.0.0/woodstox-core-lgpl-4.0.0.pom

This seems incorrect to me ( and maven also does not like it )

Could it be, that it needs redeployment under URL:
http://repository.codehaus.org/org/codehaus/woodstox/wstx-core-lgpl/4.0.0/woodstox-core-lgpl-4.0.0.pom


regarsd,

regards,
----[ Konstantin Pribluda http://www.pribluda.de ]----------------
JTec quality components: http://www.pribluda.de/projects/


     

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Cowtowncoder]

On Sun, Jan 25, 2009 at 8:48 AM, Konstantin Priblouda
<kpriblouda@...> wrote:

> Hi all,
>
> Somehow I'm unable to download WSTX 4.0.0 from maven repository.
>
> I'm using:
>        <dependency>
>           <groupId>org.codehaus.woodstox</groupId>
>           <artifactId>wstx-asl</artifactId>
>           <version>4.0.0</version>
>       </dependency>
>
> But in the codehaus repo artifacts are named like:
>
> http://repository.codehaus.org/org/codehaus/woodstox/wstx-lgpl/4.0.0/woodstox-core-lgpl-4.0.0.pom
>
> This seems incorrect to me ( and maven also does not like it )
>
> Could it be, that it needs redeployment under URL:
> http://repository.codehaus.org/org/codehaus/woodstox/wstx-core-lgpl/4.0.0/woodstox-core-lgpl-4.0.0.pom

You are absolutely right! Yes, due to renaming of artifacts for 4.0.0,
directory names need to change too.
Apologies for mess up, I will get this straightened out today.

Thank you for reporting this,

-+ Tatu +-

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Cowtowncoder]

Ok, I renamed the directory: it may take a while for the change to
propagate over to other repositories, but if this is not fixed by
tomorrow please let me know.

Thank you again Konstantin for reporting this & apologies for inconvenience.

-+ Tatu +-

On Sun, Jan 25, 2009 at 12:42 PM, Tatu Saloranta <tsaloranta@...> wrote:

> On Sun, Jan 25, 2009 at 8:48 AM, Konstantin Priblouda
> <kpriblouda@...> wrote:
>> Hi all,
>>
>> Somehow I'm unable to download WSTX 4.0.0 from maven repository.
>>
>> I'm using:
>>        <dependency>
>>           <groupId>org.codehaus.woodstox</groupId>
>>           <artifactId>wstx-asl</artifactId>
>>           <version>4.0.0</version>
>>       </dependency>
>>
>> But in the codehaus repo artifacts are named like:
>>
>> http://repository.codehaus.org/org/codehaus/woodstox/wstx-lgpl/4.0.0/woodstox-core-lgpl-4.0.0.pom
>>
>> This seems incorrect to me ( and maven also does not like it )
>>
>> Could it be, that it needs redeployment under URL:
>> http://repository.codehaus.org/org/codehaus/woodstox/wstx-core-lgpl/4.0.0/woodstox-core-lgpl-4.0.0.pom
>
> You are absolutely right! Yes, due to renaming of artifacts for 4.0.0,
> directory names need to change too.
> Apologies for mess up, I will get this straightened out today.
>
> Thank you for reporting this,
>
> -+ Tatu +-
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Konstantin Priblouda]

----[ Konstantin Pribluda http://www.pribluda.de ]----------------
JTec quality components: http://www.pribluda.de/projects/


--- On Mon, 1/26/09, Tatu Saloranta <tsaloranta@...> wrote:

> From: Tatu Saloranta <tsaloranta@...>
> Subject: Re: [woodstox-user] Correct dependency for maven 2?
> To: user@...
> Date: Monday, January 26, 2009, 7:52 AM
> Ok, I renamed the directory: it may take a while for the
> change to
> propagate over to other repositories, but if this is not
> fixed by
> tomorrow please let me know.
>
> Thank you again Konstantin for reporting this &
> apologies for inconvenience.

Nevermind, I also produce repo mishaps on codehaus ;)
BTW,  it is strange to see project without maven build.

Do you need one?

regards,


     

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Cowtowncoder]

On Mon, Jan 26, 2009 at 1:31 AM, Konstantin Priblouda
<kpriblouda@...> wrote:
>
...
> Nevermind, I also produce repo mishaps on codehaus ;)
> BTW,  it is strange to see project without maven build.

:)

Well, Woodstox has very few dependencies of its own (stax api), which
makes it less of an issue. I actually produce poms from templates
using Ant. :-)

Part of it is my inexperience with Maven; I did convert one other
project (StaxMate) to use Maven for compilation but hadn't time to
finish it up. The main hope was to simplify deployment process, since
that it's bit laborious as of now.

> Do you need one?

If that would make it easier to deploy artifacts, it would be great!
I was actually wondering how easy it would be. The only immediate
challenge I saw was the question of how to produce separate artifacts
for 2 licenses involved -- I wasn't sure what's the proper way of
doing this with Maven.

Other than that I'm sure Maven can handle things needed:

- compiling & packaging classes as binary jars, source archives
- producing javadocs
- running code coverage (cobertura currently)
- generating OSGi bundles out of jars (or building jars as bundles to
begin with)

So, I would definitely love contribution(s) to make the project Maven buildable.

-+ Tatu +-

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Konstantin Priblouda]

----[ Konstantin Pribluda http://www.pribluda.de ]----------------
JTec quality components: http://www.pribluda.de/projects/


--- On Mon, 1/26/09, Tatu Saloranta <tsaloranta@...> wrote:

> Well, Woodstox has very few dependencies of its own (stax
> api), which
> makes it less of an issue. I actually produce poms from
> templates
> using Ant. :-)

Invalid poms in wrong place though ;)

> Part of it is my inexperience with Maven; I did convert one
> other
> project (StaxMate) to use Maven for compilation but
> hadn't time to
> finish it up. The main hope was to simplify deployment
> process, since
> that it's bit laborious as of now.

I do deployments / release runs of xdoclet-plugins on regular
basis,  and it's a bit more complicated than your stuff ;)
( some 20+ subprojects on 3 levels )

> > Do you need one?
>
> If that would make it easier to deploy artifacts, it would
> be great!
> I was actually wondering how easy it would be. The only
> immediate
> challenge I saw was the question of how to produce separate
> artifacts
> for 2 licenses involved -- I wasn't sure what's the
> proper way of
> doing this with Maven.

Well, 2 different artifacts would be bit of tricky,  but with
some reorganisation of sources it would be possible

BTW,maven release plugin also takescare of tagging / branching
in svn

> Other than that I'm sure Maven can handle things
> needed:
>
> - compiling & packaging classes as binary jars, source
> archives
... by default
> - producing javadocs
... bydefault
> - running code coverage (cobertura currently)
...just add report
> - generating OSGi bundles out of jars (or building jars as
> bundles to
> begin with)
... by default

> So, I would definitely love contribution(s) to make the
> project Maven buildable.

well, as I got paid use case for high performance xml pull parser,
I also got time to do this ( and my customer would like  to have sane
maven builds )

regards,


     

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Cowtowncoder]

On Mon, Jan 26, 2009 at 9:24 AM, Konstantin Priblouda
<kpriblouda@...> wrote:
> --- On Mon, 1/26/09, Tatu Saloranta <tsaloranta@...> wrote:
>
>> Well, Woodstox has very few dependencies of its own (stax api), which
>> makes it less of an issue. I actually produce poms from
>> templates using Ant. :-)
>
> Invalid poms in wrong place though ;)

Yeah there are some downsides to this! :-)

Actually, I did add xml validation to at least verify that results are
well-formed. But that only goes so far, since task doesn't really
understand what is being done.

...
> I do deployments / release runs of xdoclet-plugins on regular
> basis,  and it's a bit more complicated than your stuff ;)
> ( some 20+ subprojects on 3 levels )

Sure, I am not doubting Maven's capabilities at all. Especially given
that it was built to help with bigger projects.

>> for 2 licenses involved -- I wasn't sure what's the proper way of
>> doing this with Maven.
>
> Well, 2 different artifacts would be bit of tricky,  but with
> some reorganisation of sources it would be possible

Good, I thought it should be, given configurability. Source code has
to be reorged anyways, to add the exrta dirs (which I'm not big fan
of, but I'm sure I get used to it quick enough),.

> BTW,maven release plugin also takescare of tagging / branching in svn

Ok. That's relatively easy with svn anyways, but at least I wouldn't
have to refer to svn docs each time. Or forget to tag things when they
should be...

>> Other than that I'm sure Maven can handle things
...
>> So, I would definitely love contribution(s) to make the
>> project Maven buildable.
>
> well, as I got paid use case for high performance xml pull parser,
> I also got time to do this ( and my customer would like  to have sane
> maven builds )

Very cool! Let me know if I can help. Besides, this is perfect time to
do it, now that 4.0 final was just released.

The only thing besides contribution I would need is to get a
Contributor Agreement form filled: it's under
DEV/constributor-agreement.pdf.
It is one written by Sun for their open source projects so there
should be absolutely nothing weird. But I do need to keep track of
these, so that corporate entities do not have to go through process of
verification each time they want to distribute Woodstox (been the case
with Eclipse plug-ins lately).

-+ Tatu +-

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Cowtowncoder]

Argh. I mis-renamed it first, so here's the bug entry:

http://jira.codehaus.org/browse/WSTX-185

I'll try to build a dummy Maven project to verify that I got the dir
right now; it should be, but better safe than sorry.

-+ Tatu +-

On Sun, Jan 25, 2009 at 9:52 PM, Tatu Saloranta <tsaloranta@...> wrote:

> Ok, I renamed the directory: it may take a while for the change to
> propagate over to other repositories, but if this is not fixed by
> tomorrow please let me know.
>
> Thank you again Konstantin for reporting this & apologies for inconvenience.
>
> -+ Tatu +-
>
> On Sun, Jan 25, 2009 at 12:42 PM, Tatu Saloranta <tsaloranta@...> wrote:
>> On Sun, Jan 25, 2009 at 8:48 AM, Konstantin Priblouda
>> <kpriblouda@...> wrote:
>>> Hi all,
>>>
>>> Somehow I'm unable to download WSTX 4.0.0 from maven repository.
>>>
>>> I'm using:
>>>        <dependency>
>>>           <groupId>org.codehaus.woodstox</groupId>
>>>           <artifactId>wstx-asl</artifactId>
>>>           <version>4.0.0</version>
>>>       </dependency>
>>>
>>> But in the codehaus repo artifacts are named like:
>>>
>>> http://repository.codehaus.org/org/codehaus/woodstox/wstx-lgpl/4.0.0/woodstox-core-lgpl-4.0.0.pom
>>>
>>> This seems incorrect to me ( and maven also does not like it )
>>>
>>> Could it be, that it needs redeployment under URL:
>>> http://repository.codehaus.org/org/codehaus/woodstox/wstx-core-lgpl/4.0.0/woodstox-core-lgpl-4.0.0.pom
>>
>> You are absolutely right! Yes, due to renaming of artifacts for 4.0.0,
>> directory names need to change too.
>> Apologies for mess up, I will get this straightened out today.
>>
>> Thank you for reporting this,
>>
>> -+ Tatu +-
>>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email