I have committed the split metadata now. The details are below. I'd like to get feedback from the projects that use it. I couldn't execute mvn deploy. It would fail with e.g. [INFO] Error retrieving previous build number for artifact 'org.jboss.metadata:metadata-common:jar': repository metadata for: 'snapshot org.jboss.meta data:metadata-common:2.0.0-SNAPSHOT' could not be retrieved from repository: snapshots.jboss.org due to an error: Authorization failed: Not authorized So, if you want to build e.g. EJB metadata you have to check out ejb and common projects, build and install common and then build ejb. New metadata structure ---------------------- Metadata project (version 1.0.X) has been split into several: common project + one project per specific technology. The initial version for all the new projects is 2.0.0-SNAPSHOT. The current list of the projects is: - common - EJB - WEB - RAR - EAR - client The common one contains stuff which is used by other projects, plus common Java EE metadata, common JBoss metadata and WS metadata. These could further be extracted to their own projects if needed. All technology-specific projects declare dependency on the common project. SVN repository -------------- The main location is https://svn.jboss.org/repos/jbossas/projects/metadata/. Under which each project's trunk is located under project_name/trunk, e.g. common/trunk, ejb/trunk, etc. Maven ----- groupId remains the same, i.e. org.jboss.metadata. artifactId is metadata-project_name, e.g. metadata-common, metadata-ejb, etc. Things that were removed ------------------------ Packages org.jboss.ejb3.metamodel and org.jboss.metamodel.descriptor weren't copied. I am not sure if they are used now. The same for org.jboss.metadata.test.ejb3 and org.jboss.metadata.test.generator. JAWS DTDs weren't copied neither (they shouldn't have been there from the beginning). _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

I have committed the split metadata now. The details are below. I'd like to get feedback from the projects that use it.

New metadata structure ---------------------- Metadata project (version 1.0.X) has been split into several: common project + one project per specific technology. The initial version for all the new projects is 2.0.0-SNAPSHOT. The current list of the projects is: - common - EJB - WEB - RAR - EAR - client The common one contains stuff which is used by other projects, plus common Java EE metadata, common JBoss metadata and WS metadata. These could further be extracted to their own projects if needed. All technology-specific projects declare dependency on the common project.

Ok, committed. The metadata versions are now at 2.0.0.Alpha. I've changed the maven artifactId of the projects to jboss-metadata-project_name to follow other projects. I haven't split common further for now. But I am also not against it. Jesper Pedersen wrote: > Hi Alexey. > > On Wednesday 17 June 2009 09:35:03 Alexey Loubyansky wrote: >> I have committed the split metadata now. The details are below. I'd like >> to get feedback from the projects that use it. >> > > Excellent :) > >> New metadata structure >> ---------------------- >> >> Metadata project (version 1.0.X) has been split into several: common >> project + one project per specific technology. The initial version for >> all the new projects is 2.0.0-SNAPSHOT. The current list of the projects >> is: - common >> - EJB >> - WEB >> - RAR >> - EAR >> - client >> >> The common one contains stuff which is used by other projects, plus >> common Java EE metadata, common JBoss metadata and WS metadata. These >> could further be extracted to their own projects if needed. >> All technology-specific projects declare dependency on the common >> project. >> > > Perhaps the common module can be split even more. > > I see some classes that are marked as @Deprecated - since this is a > 2.0 version these could be moved to a "legacy" module. > > Also I think that the common module only should contain the classes > actually needed by the sub-projects - and thereby provide a common core. > > I'm thinking about the org.jboss.metadata.javaee.spec and classes in > the top-level org.jboss.metadata package - could be moved to a > javaee-spec module. And there are other examples. > > The Tattletale report for the RAR module shows that > org/jboss/metadata/annotation/** > org/jboss/metadata/javaee/support/* > > are needed - so those are candidates to stay in the common module IMHO. > > Best regards, > Jesper

We can't have Jira projects for each and every component that has its own release cycle. That would make Jira flooded with projects. Meanwhile vote: http://jira.atlassian.com/browse/JRA-2744 http://jira.atlassian.com/browse/JRA-3228 and http://jira.atlassian.com/browse/JRA-3501 :-) Carlo Alexey Loubyansky wrote: > Replied to the wrong thread. I meant to say the AS trunk is now using > the new split metadata. > > I guess we need new Jira projects for each metadata project. > > Alexey Loubyansky wrote: > > >> Ok, committed. The metadata versions are now at 2.0.0.Alpha. >> >> I've changed the maven artifactId of the projects to >> jboss-metadata-project_name to follow other projects. >> >> I haven't split common further for now. But I am also not against it. >> >> Jesper Pedersen wrote: >> >> >>> Hi Alexey. >>> >>> On Wednesday 17 June 2009 09:35:03 Alexey Loubyansky wrote: >>> >>> >>>> I have committed the split metadata now. The details are below. I'd like >>>> to get feedback from the projects that use it. >>>> >>>> >>>> >>> Excellent :) >>> >>> >>> >>>> New metadata structure >>>> ---------------------- >>>> >>>> Metadata project (version 1.0.X) has been split into several: common >>>> project + one project per specific technology. The initial version for >>>> all the new projects is 2.0.0-SNAPSHOT. The current list of the projects >>>> is: - common >>>> - EJB >>>> - WEB >>>> - RAR >>>> - EAR >>>> - client >>>> >>>> The common one contains stuff which is used by other projects, plus >>>> common Java EE metadata, common JBoss metadata and WS metadata. These >>>> could further be extracted to their own projects if needed. >>>> All technology-specific projects declare dependency on the common >>>> project. >>>> >>>> >>>> >>> Perhaps the common module can be split even more. >>> >>> I see some classes that are marked as @Deprecated - since this is a >>> 2.0 version these could be moved to a "legacy" module. >>> >>> Also I think that the common module only should contain the classes >>> actually needed by the sub-projects - and thereby provide a common core. >>> >>> I'm thinking about the org.jboss.metadata.javaee.spec and classes in >>> the top-level org.jboss.metadata package - could be moved to a >>> javaee-spec module. And there are other examples. >>> >>> The Tattletale report for the RAR module shows that >>> org/jboss/metadata/annotation/** >>> org/jboss/metadata/javaee/support/* >>> >>> are needed - so those are candidates to stay in the common module IMHO. >>> >>> Best regards, >>> Jesper >>> >>> > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development > > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development