[jboss-dev] why strip version from jarnames?

[Richard Opalka]

-1

Using versioned jars in AS is road to maintainance hell IMHO :(
Note that there are some shell scripts in AS/bin
and many !/META-INF/MANIFEST.MF/Class-Path entries
in many jars referencing distribution jars.
And these scripts and jars usually have different lifecycle
(coming from different projects) than AS has.

Rio

On 02/01/2010 04:42 AM, Paul Gier wrote:
> When I switched the build to Maven I just kept the jars without versions because
> that's how it was before.  There are still a few places that refer to the
> specific jars names, but we can change this if we want.  As Adrian said, most of
> the testsuite jar references are created automatically, so it would only be an
> issue for the few that still refer directly to the name.
>
> Anil Saldhana wrote:
>    
>> Think there was a discussion on this 2 years ago. Cannot remember the reasons for the opposition
>> except that pre-maven builds/releases had no version names and we *maybe* decided to retain the process.
>>
>> One other reason may be that our build was not completely mavenized so all testsuite classpaths would
>> have to be updated with the version numbers in the jars.
>>
>>
>> On 01/29/2010 08:29 PM, Bill Burke wrote:
>>
>>      
>>> Just wondering, why strip version tags from jar names in jboss AS
>>> distribution?  Is this just practice or a requirement?
>>>
>>>        
>> _______________________________________________
>> 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
>    


-- 
Richard Opalka
ropalka at redhat.com
JBoss, by Red Hat

Office: +420 222 365 200
Mobile: +420 731 186 942