[jboss-dev] Moving AS5 trunk away from snapshots

[Paul Gier]

It downloaded the new one ok for me when I changed it locally.  I had to change 
it in component-info/pom.xml and thirdparty/pom.xml.  I also should have 
mentioned before that the metadata artifact is mapped to the old name in the 
thirdparty directory.  So in the thirdparty/pom.xml you'll have to change the 
groupId in the thirdparty mapping configuration.  If you search for 
jboss-metadata you will find it.

So change from this

             <dependency>
               <groupId>org.jboss</groupId>
               <artifactId>jboss-metadata</artifactId>
               <mapping>
                 <componentId>jboss.metadata</componentId>
               </mapping>
             </dependency>

to this
             <dependency>
               <groupId>org.jboss.metadata</groupId>
               <artifactId>jboss-metadata</artifactId>
               <mapping>
                 <componentId>jboss.metadata</componentId>
               </mapping>
             </dependency>

Otherwise the maven plugin will put the new download under
thirdparty/org/jboss/metadata/lib

Let me know if that doesn't fix it.


Dimitris Andreadis wrote:
> Ok, so this is done; AS trunk points now to 
> org.jboss.metadata:jboss-metadata and builds Okay (at least locally).
> 
> Now, I switch the component-matrix/pol.xml from 1.0.0-SNAPSHOT to the 
> 1.0.0.Beta7 version, but when I try to re-build it doesn't detect the 
> change to download the new library.
> 
>       <dependency>
>         <groupId>org.jboss.metadata</groupId>
>         <artifactId>jboss-metadata</artifactId>
>         <version>1.0.0.Beta7</version>
>       </dependency>
> 
> How is this supposed to work?
> 
> Paul Gier wrote:
>> Add them to the component-matrix pom in the dependencyManagement 
>> section.  That way the exclusions should take effect through all app 
>> server poms.
>>
>> Dimitris Andreadis wrote:
>>> Paul, add exclusions to which pom? component-matrix dir? thirdparty dir?
>>>
>>> Paul Gier wrote:
>>>> I'm definitely in favor of this change, but one of the things to be 
>>>> aware of when changing a groupId is that maven will no longer be 
>>>> able to determine that older versions are the same artifact.  So it 
>>>> may not be able to properly version manage the transitive dependencies.
>>>>
>>>> After you make the change you might want to run dependency:tree and 
>>>> add exclusions where the old groupId/artifactId is picked up 
>>>> transitively.
>>>>
>>>> Dimitris Andreadis wrote:
>>>>> I've just uploaded a snapshot of the latest jboss-metadata with an 
>>>>> updated pom:
>>>>> https://snapshots.jboss.org/maven2/org/jboss/jboss-metadata/1.0.0-SNAPSHOT/ 
>>>>>
>>>>>
>>>>> I want to release it as 1.0.0.Beta7, and possibly change the 
>>>>> groupId to 'org.jboss.metadata', so please speak is you see any 
>>>>> issues with that.
>>>>>
>>>>> Scott Stark wrote:
>>>>>> metadata could go to 1.0.0.Beta7, check with Alexey
>>>>>> jboss-javaee Shelly had a question on this. All we have done is 
>>>>>> drop the jboss-jaxs-api as far as I know.
>>>>>>
>>>>>> Dimitris Andreadis wrote:
>>>>>>> To test the effectiveness of the maven thirdparty build and to 
>>>>>>> increase the stability of AS trunk, we need to move away from 
>>>>>>> snapshot versions and avoid introducing new ones, asap. It's 
>>>>>>> doesn't have to be the final version that will go in AS5 CR1, any 
>>>>>>> intermediate tagged release would do.
>>>>>>>
>>>>>>> There are currently quite a few snapshots:
>>>>>>>
>>>>>>> - ejb3
>>>>>>> - security
>>>>>>> - jbossws
>>>>>>> - javaee-ee
>>>>>>> - vfs
>>>>>>> - metadata
>>>>>>>
>>>>>>> We monitor component updates here:
>>>>>>> http://jira.jboss.com/jira/browse/JBAS-5121
>>>>>>>
>>>>>>> Another important on-going and potentially longer term effort is 
>>>>>>> to keep creating integration SPIs, wherever are missing, in order 
>>>>>>> to remove any remaining cyclical dependencies.
>>>>>>>
>>>>>>> Cheers
>>>>>>> /Dimitris
>>>>>>> _______________________________________________
>>>>>>> jboss-development mailing list
>>>>>>> jboss-development at lists.jboss.org
>>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>>>
>>>>>> _______________________________________________
>>>>>> jboss-development mailing list
>>>>>> jboss-development at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>> _______________________________________________
>>>>> jboss-development mailing list
>>>>> jboss-development at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>
>>>> _______________________________________________
>>>> jboss-development mailing list
>>>> jboss-development at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development