I just finished the integration of Brett's new maven-one-plugin,
which adds the ability to publish to both an m1 and m2 remote
repository. To publish jars simply execute "mvn deploy" from the
root or from within a module. The m2 deployment code doesn't seem to
set the permissions correctly on the uploaded jars, so if you get
permission denied in from an upload bug Brett :) as it is his bug to
fix (and he has root on codehaus so he can fix it two ways)
-dain
On Nov 1, 2005, at 9:38 AM, Dain Sundstrom wrote:
> For those of you that missed it, we are now completely on maven 2.
>
> We are using the standard maven 2 directory structure (http://
> maven.apache.org/guides/introduction/introduction-to-the-standard-
> directory-layout.html), which means an extra directory between a
> module root and the source (e.g. kernel/src/main/java). The
> advantages of this structure, become obvious as you add extra
> source types, and with resources. Resources are now kept in src/
> main/resources and src/test/resources. M2 will automatically add
> all files from resources to the respective bundle, and
> automatically adds the resources dir as a source dir in idea.
>
> Speaking of idea, the idea plugin really blows right now. For
> example, it generates the wrong Java version name, doesn't mount
> the root module, and doesn't link the modules. The nice think is
> XBean is a small project, so this can be fixed in seconds. The
> correct dependencies are:
>
> jmx --> kernel and spring
> server --> kernel and spring
>
> The XBean build uses the maven-one-plugin, Brett wrote last night,
> which publishes jars to both you maven 1 and maven 2 local
> repositories, so you should be able to seamlessly develop XBean and
> maven 1 projects on the same machine. As for the remote
> repository, I'm still working on that.
>
> If you have any problems, I'm on IRC.
>
> -dain
>
