[prev in list] [next in list] [prev in thread] [next in thread] 

List:       maven-user
Subject:    Handling Non-Public runtime packages
From:       Steve Cohen <stevecoh1 () comcast ! net>
Date:       2011-12-01 20:00:14
Message-ID: 4ED7DCCE.2010307 () comcast ! net
[Download RAW message or body]


I am perplexed by the following situation:

I work for a very large corporation with strict bureaucratic rules about 
what you can use.  Nonetheless, they have a maven repository 
administered by very helpful people.  However the maven repository 
people don't talk so much to the technical standards people (they don't 
even know each other) and therein lies the problem.

The technical standards folks mandate that certain versions of 
application servers (for example, JBoss) must be used.  These are not 
the publicly available versions commonly found but "enterprise versions" 
that are either built by RedHat for specific corporate clients or 
available to any paying corporate client, I'm not sure which.  These 
come packaged in .zip files that may be downloaded from an internal 
corporate web site.

That would be okay if all I was concerned about was creating a server to 
develop on.  But I also need to develop against the "targeted runtime" 
of that server, and I want to use Maven, as I could with the publicly 
available versions of the server.  To do that, I need to have these 
server runtime jars as "Provided" dependencies in my project.  However, 
there are no poms included with this zip file.  I could load every jar 
in the package into a team-private "third party" repo in the central 
repo, but this would then be just a bunch of jars with no 
inter-dependency information available.  Even if POMs were available, 
getting them all into the repository is a non-trivial task.

How does one cope with this situation?



["smime.p7s" (application/pkcs7-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]