see comments inline and please use the mailing list for communication as other people can find this useful too
On 8/15/07, Piotr Tabor <[EMAIL PROTECTED]> wrote: > Hi Carlos, > > Do you really need plexus- for compilation? your code > > shouldn't probably be aware of that one, at most just the plexus api > > should be needed > > > I can compile my code with either container-default or component-api. > But if I build it > with container-api I will receive such a error (if the connector is run > by plugin): > > java.lang.LinkageError: loader constraint violation: when resolving > method > "org.codehaus.plexus.configuration.xml.XmlPlexusConfiguration.getChild(Ljava/lang/String;)Lorg/codehaus/plexus/configuration/PlexusConfiguration;" > the class loader (instance of org/codehaus/classworlds/RealmClassLoader) > of the current class, > org/apache/maven/diagrams/connector_api/descriptor/ConnectorDescriptorBuilder, > and the class loader (instance of > org/codehaus/classworlds/RealmClassLoader) for resolved class, > org/codehaus/plexus/configuration/xml/XmlPlexusConfiguration, have > different Class objects for the type > org/codehaus/plexus/configuration/PlexusConfiguration used in the signature" > > I haven't find API that is compatible with plexus-container-default - > 1.0-alpha-9-stable-1 ( used in Maven 2.0.7). Try depending on the API with compile scope and on the container-default with runtime scope. That way you prevent adding inadvertently dependencies on the container at compile time > > > > Using org.apache.maven as groupId is not a good idea, you should > > extend the mojo sandbox parent pom, so you can deploy snapshots to the > > codehaus repo. > > > I am participing in GSOC with ASF as a Mentoring Organization. I > expected that my code will by moved > to maven's sandbox - so I'm using ASF's groupId. I hoped that codehaus > is only "temporary". yes, and it' s not going to be a problem later, just a search and replace, but you can use the codehaus infrastructure now to deploy snapshots so other people can try it easily. > > The prefuse snapshot you can put it in the mojo snapshot repository > > dav:https://dav.codehaus.org/snapshots.repository/mojo/ but in the > > org.codehaus.mojo groupId so it doesn't clash with the official one > > and I think it won't be available under any other groupId. Do you > > really need a snapshot? > > > > The prefuse jar seems to be compiled under Java 6, because I have 5 > > and I get this error > > > > > I rebuilded this artifact with Java 1.5. It is still on SVN. In > README file is command to upload it > to local repo. If want to which groupId use for this artifact before I > will upload it to repo: > a) org.codehaus.mojo.sandbox.maven-diagram-maker.prefuse > b) org.codehaus.mojo.maven-diagram-maker.prefuse I'd say b) > > I corrected some bugs in Prefuse - so I would like to use project with > corrected version of prefuse. The > project will also work /compile with official version. Unfortunetelly > prefuse seems to be dead project (I haven't noticed > any changes on its SVN for at least one year). > > I got a test error > > testGetMavenProject(org.apache.maven.diagrams.connector_api.context.RunMavenConnectorContextTest) > > > > > > > I hope it is already corrected. now I get it a test error in test(org.apache.maven.diagrams.connectors.classes.PackageUtilsTest) java.lang.NullPointerException at org.apache.maven.diagrams.connectors.classes.PackageUtilsTest.test(PackageUtilsTest.java:41) at org.apache.maven.diagrams.connectors.classes.PackageUtilsTest.test(PackageUtilsTest.java:41) I'll try to run it later > > > > Also you need to configure SVN as explained in > > http://maven.apache.org/developers/committer-environment.html > > so the files have the right line ending in linux and windows > > > Done. > > I'll give it another try when some issues get solved > > > Thank you very, very much for your help and advice. > > Piotr Tabor > > -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
