You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Kristian Waagan <kr...@apache.org> on 2009/06/10 09:22:38 UTC
Apache Derby artifacts for Maven 2
Hello,
According to [1], I'm mailing you to get some help. I'm an Apache Derby
committer.
The Apache Derby Maven 1 artifacts are no longer automatically converted
to Maven 2. As can be seen in [2], all our releases are there. In [3]
however, the last release (10.5.1.1) is missing. Release information for
the project can be found at [4].
Can you think of anything that has changed lately, that would affect the
conversion and publishing of the Maven 2 artifacts for Derby?
Does the Derby project need to take steps to fix the issue?
If so, where can I find the necessary information?
Finally, there is some information at [5], and [6] describes our release
process (search for maven).
Thank you,
--
Kristian
[1] http://maven.apache.org/project-faq.html
[2]
http://people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.derby/jars/
[3] http://repo1.maven.org/maven2/org/apache/derby/derby/
[4] http://projects.apache.org/projects/derby.html
[5] https://issues.apache.org/jira/browse/DERBY-1378
[6] http://wiki.apache.org/db-derby/DerbySnapshotOrRelease
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Apache Derby artifacts for Maven 2
Posted by Brett Porter <br...@apache.org>.
On 11/06/2009, at 2:00 AM, Brian Fox wrote:
> On Wed, Jun 10, 2009 at 11:31 AM, Kristian
> Waagan<kr...@apache.org> wrote:
>> Brian Fox wrote:
>>>
>>> The auto conversion to m2 artifacts has been stopped, and it's a
>>> manual process now. You should plan to produce M2 artifacts going
>>> forward to get things automatically synced. We can do the conversion
>>> for the existing release.
>>
>> Thank you, Brian.
>>
>> If one of you is willing to convert the Derby 10.5.1.1 artifacts,
>> that will
>> be much appreciated!
>>
>>
>> Not being very familiar with Maven, I have some newbie questions;
>> 1a) If we start producing M2 artifacts and publish these, will
>> that result
>> in M1 artifacts being created automatically outside of the Derby
>> project?
>
> Nexus is able to convert m2 back to m1 for those that actually need
> it, so this isn't a concern.
Users don't need to use the Nexus instance though, the central
repository automatically rewrites m1 requests onto the m2 repository
there.
Basically, publish them to the m2 repo and m1 users will be taken care
of automatically.
>
>> 1b) Should we be producing both versions?
>
> No, M2 is the standard now.
>
>> 2a) Is it good enough to keep converting the M1 artifacts?
>> 2b) Will the conversion be fully automatic once we have the tools
>> set up?
>
> N/A
>
>> 3) Is M1 considered obsolete?
>
> Yes.
>
>>
>>
>> Regards,
>> --
>> Kristian
>>
>>>
>>> On Wed, Jun 10, 2009 at 3:22 AM, Kristian
>>> Waagan<kr...@apache.org>
>>> wrote:
>>>>
>>>> Hello,
>>>>
>>>> According to [1], I'm mailing you to get some help. I'm an Apache
>>>> Derby
>>>> committer.
>>>> The Apache Derby Maven 1 artifacts are no longer automatically
>>>> converted
>>>> to
>>>> Maven 2. As can be seen in [2], all our releases are there. In [3]
>>>> however,
>>>> the last release (10.5.1.1) is missing. Release information for the
>>>> project
>>>> can be found at [4].
>>>>
>>>> Can you think of anything that has changed lately, that would
>>>> affect the
>>>> conversion and publishing of the Maven 2 artifacts for Derby?
>>>> Does the Derby project need to take steps to fix the issue?
>>>> If so, where can I find the necessary information?
>>>>
>>>> Finally, there is some information at [5], and [6] describes our
>>>> release
>>>> process (search for maven).
>>>>
>>>>
>>>> Thank you,
>>>> --
>>>> Kristian
>>>>
>>>>
>>>> [1] http://maven.apache.org/project-faq.html
>>>> [2]
>>>>
>>>> http://people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.derby/jars/
>>>> [3] http://repo1.maven.org/maven2/org/apache/derby/derby/
>>>> [4] http://projects.apache.org/projects/derby.html
>>>> [5] https://issues.apache.org/jira/browse/DERBY-1378
>>>> [6] http://wiki.apache.org/db-derby/DerbySnapshotOrRelease
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Apache Derby artifacts for Maven 2
Posted by Brian Fox <br...@infinity.nu>.
On Wed, Jun 10, 2009 at 11:31 AM, Kristian Waagan<kr...@apache.org> wrote:
> Brian Fox wrote:
>>
>> The auto conversion to m2 artifacts has been stopped, and it's a
>> manual process now. You should plan to produce M2 artifacts going
>> forward to get things automatically synced. We can do the conversion
>> for the existing release.
>
> Thank you, Brian.
>
> If one of you is willing to convert the Derby 10.5.1.1 artifacts, that will
> be much appreciated!
>
>
> Not being very familiar with Maven, I have some newbie questions;
> 1a) If we start producing M2 artifacts and publish these, will that result
> in M1 artifacts being created automatically outside of the Derby project?
Nexus is able to convert m2 back to m1 for those that actually need
it, so this isn't a concern.
> 1b) Should we be producing both versions?
No, M2 is the standard now.
> 2a) Is it good enough to keep converting the M1 artifacts?
> 2b) Will the conversion be fully automatic once we have the tools set up?
N/A
> 3) Is M1 considered obsolete?
Yes.
>
>
> Regards,
> --
> Kristian
>
>>
>> On Wed, Jun 10, 2009 at 3:22 AM, Kristian Waagan<kr...@apache.org>
>> wrote:
>>>
>>> Hello,
>>>
>>> According to [1], I'm mailing you to get some help. I'm an Apache Derby
>>> committer.
>>> The Apache Derby Maven 1 artifacts are no longer automatically converted
>>> to
>>> Maven 2. As can be seen in [2], all our releases are there. In [3]
>>> however,
>>> the last release (10.5.1.1) is missing. Release information for the
>>> project
>>> can be found at [4].
>>>
>>> Can you think of anything that has changed lately, that would affect the
>>> conversion and publishing of the Maven 2 artifacts for Derby?
>>> Does the Derby project need to take steps to fix the issue?
>>> If so, where can I find the necessary information?
>>>
>>> Finally, there is some information at [5], and [6] describes our release
>>> process (search for maven).
>>>
>>>
>>> Thank you,
>>> --
>>> Kristian
>>>
>>>
>>> [1] http://maven.apache.org/project-faq.html
>>> [2]
>>>
>>> http://people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.derby/jars/
>>> [3] http://repo1.maven.org/maven2/org/apache/derby/derby/
>>> [4] http://projects.apache.org/projects/derby.html
>>> [5] https://issues.apache.org/jira/browse/DERBY-1378
>>> [6] http://wiki.apache.org/db-derby/DerbySnapshotOrRelease
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Apache Derby artifacts for Maven 2
Posted by Kristian Waagan <kr...@apache.org>.
Brian Fox wrote:
> The auto conversion to m2 artifacts has been stopped, and it's a
> manual process now. You should plan to produce M2 artifacts going
> forward to get things automatically synced. We can do the conversion
> for the existing release.
Thank you, Brian.
If one of you is willing to convert the Derby 10.5.1.1 artifacts, that
will be much appreciated!
Not being very familiar with Maven, I have some newbie questions;
1a) If we start producing M2 artifacts and publish these, will that
result in M1 artifacts being created automatically outside of the Derby
project?
1b) Should we be producing both versions?
2a) Is it good enough to keep converting the M1 artifacts?
2b) Will the conversion be fully automatic once we have the tools set up?
3) Is M1 considered obsolete?
Regards,
--
Kristian
>
> On Wed, Jun 10, 2009 at 3:22 AM, Kristian Waagan<kr...@apache.org> wrote:
>> Hello,
>>
>> According to [1], I'm mailing you to get some help. I'm an Apache Derby
>> committer.
>> The Apache Derby Maven 1 artifacts are no longer automatically converted to
>> Maven 2. As can be seen in [2], all our releases are there. In [3] however,
>> the last release (10.5.1.1) is missing. Release information for the project
>> can be found at [4].
>>
>> Can you think of anything that has changed lately, that would affect the
>> conversion and publishing of the Maven 2 artifacts for Derby?
>> Does the Derby project need to take steps to fix the issue?
>> If so, where can I find the necessary information?
>>
>> Finally, there is some information at [5], and [6] describes our release
>> process (search for maven).
>>
>>
>> Thank you,
>> --
>> Kristian
>>
>>
>> [1] http://maven.apache.org/project-faq.html
>> [2]
>> http://people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.derby/jars/
>> [3] http://repo1.maven.org/maven2/org/apache/derby/derby/
>> [4] http://projects.apache.org/projects/derby.html
>> [5] https://issues.apache.org/jira/browse/DERBY-1378
>> [6] http://wiki.apache.org/db-derby/DerbySnapshotOrRelease
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Apache Derby artifacts for Maven 2
Posted by Brian Fox <br...@infinity.nu>.
The auto conversion to m2 artifacts has been stopped, and it's a
manual process now. You should plan to produce M2 artifacts going
forward to get things automatically synced. We can do the conversion
for the existing release.
On Wed, Jun 10, 2009 at 3:22 AM, Kristian Waagan<kr...@apache.org> wrote:
> Hello,
>
> According to [1], I'm mailing you to get some help. I'm an Apache Derby
> committer.
> The Apache Derby Maven 1 artifacts are no longer automatically converted to
> Maven 2. As can be seen in [2], all our releases are there. In [3] however,
> the last release (10.5.1.1) is missing. Release information for the project
> can be found at [4].
>
> Can you think of anything that has changed lately, that would affect the
> conversion and publishing of the Maven 2 artifacts for Derby?
> Does the Derby project need to take steps to fix the issue?
> If so, where can I find the necessary information?
>
> Finally, there is some information at [5], and [6] describes our release
> process (search for maven).
>
>
> Thank you,
> --
> Kristian
>
>
> [1] http://maven.apache.org/project-faq.html
> [2]
> http://people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.derby/jars/
> [3] http://repo1.maven.org/maven2/org/apache/derby/derby/
> [4] http://projects.apache.org/projects/derby.html
> [5] https://issues.apache.org/jira/browse/DERBY-1378
> [6] http://wiki.apache.org/db-derby/DerbySnapshotOrRelease
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org