got it... like the idea (useful for others besides wicket as well)
That is sort of done already with the groupId/artifactId structure,
but I get what you going for here.
It would be fairly trivial to add meta data to the library but its
much more of a pain to crawl that... what would be better if there was
some way to add indexing information to the Maven metadata that
already resides in the repos.
e.g. see:
http://repo1.maven.org/maven2/activemq/activemq-axis/maven-metadata.xml
Failing that, the POM which is more likely possible without making
changes to Maven.
There is also something that Archiva does with repos where it adds
some sort of index... some of that work might be utilized as a scraper.
Anyway, interesting idea.
- Brill
On 18-Jun-08, at 9:56 AM, Jonathan Locke wrote:
why not crawl a whole list of repos? or as many as we can find?
Brill Pappin wrote:
Don't we already have that with Maven?
I like the idea but I think that the minor extra step of turning your
"shared" components into their own module is a good thing, keeps
everything sane.
However it might be nice to have a repo that can publish all this to
(the repo1 server is a pain to get things published to.
As we work, we'll be publishing some of it to a public repo that
others can reference, however we're not there yet. I think most other
groups using maven use their own repo (but that might be a pipe
dream)... so what we really need is a place to publish our open repos
that contain wicket related stuff (assuming wicket-stuff isn't
suitable).
- Brill Pappin
On 18-Jun-08, at 5:49 AM, Jonathan Locke wrote:
my RSI is bad so please forgive the terseness. the idea:
- make an automated wicket component library
- define packaging structure for wicket library components
- structure of package would define component metadata like svn,
faq, help,
etc (probably in meta.inf created from maven pom info by maven guru)
- (only signed) jars could be automatically picked up by some naming
pattern from maven repos and deployed as live demos
- container would be simple to write (no db hassles... just use
maven and
packaging)
- everyone makes their components and demos in a standard way so we
can
stop asking around about what functionality exists
--
View this message in context:
http://www.nabble.com/idea%3A-automatic-component-repo-tp17979177p17979177.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/idea%3A-automatic-component-repo-tp17979177p17983260.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
