[
https://issues.apache.org/jira/browse/WICKET-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089253#comment-13089253
]
Andreas Pieber commented on WICKET-3976:
----------------------------------------
TBH I don't like the idea of shading the artifacts under the osgi artifact.
Since we really want to use e.g. spring and/or other artifacts the inclusions
would be too much of a hassle for osgi devs.
Just to make this clear: it does not hit me personally if we remove this patch
again. In that case it was a prototype and we've decided that it wasn't a good
idea. I've experimented with maven a little bit this morning. I tried to add a
wicket-all-package, using wicket-jar as pom again and doing a switch according
to an environment variable at runtime. In theory this would have allowed you
that you reference the production-all-in-one-jar during your app development
and a simple eclipse:ecipse with e.g. (export/set dev=true) should have
switched to the three internal jars. But maven obvious does not like this kind
of "runtime-profile-switching" :-(
IMHO this leads to the only alternative solution: OSGIfying all three modules
using split-package. This is, as often said, anything but "best-practice" but
for 1.x it has to do and for 2.x we can change the namespaces of wicket anyhow.
WDYT?
> Hide internal sub-modules from users by not deploying them in Maven
> repositories
> --------------------------------------------------------------------------------
>
> Key: WICKET-3976
> URL: https://issues.apache.org/jira/browse/WICKET-3976
> Project: Wicket
> Issue Type: Task
> Components: wicket
> Affects Versions: 1.5-RC5.1
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Priority: Minor
> Attachments: WICKET-3976.patch
>
>
> Creating this ticket in relation to the vote thread about OSGi integration
> http://markmail.org/thread/2iw5wjpn44m4grlx and
> http://markmail.org/thread/wdasrq4caft2spqj.
> The goal is to hide modules wicket-util, wicket-request and wicket-core from
> Wicket's users by not deploying them in Maven central repository.
> org.apache.wicket:wicket:jar module which will contain the classes from all
> these will be deployed instead.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
