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<[email protected]> 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: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
