Re: maven-shade-plugin and Eclipse (m2e)

[Ron Wheeler]

http://blog.artifact-software.com/tech/?p=121 and other Maven posts 
might give you some ideas about handling large numbers of third party 
jars in a large project.

We use Eclipse/STS and Maven.

Ron

On 30/06/2016 11:10 AM, Eddie Galvez wrote:

What is the way to use the maven-shade-plugin but, what I think is the
obvious usage then of such a shaded project, to have it in eclipse as a
source project?

In other words - because maven-shade-plugin only does its thing on
package... while you are in Eclipse (your IDE), other projects will not
compile since they are expecting the shaded package names... what's the way
to be able to work with a project that you want to maven-shade-plugin some
third party dependencies in, for use within and inside eclipse?

Cleary I understand you can just package/install the shaded project into a
repository then NOT bring in the source project into the workspace... but
ideally I don't want that.

Thanks!




--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: maven-shade-plugin and Eclipse (m2e)

[Aliaksei Lahachou]

Hi!

I think nothing should depend on shaded names. Everything should use
original names, which is then fixed by the shade plugin during packaging.

Regards,
Aliaksei

On Thu, Jun 30, 2016 at 5:10 PM, Eddie Galvez  wrote:

> What is the way to use the maven-shade-plugin but, what I think is the
> obvious usage then of such a shaded project, to have it in eclipse as a
> source project?
>
> In other words - because maven-shade-plugin only does its thing on
> package... while you are in Eclipse (your IDE), other projects will not
> compile since they are expecting the shaded package names... what's the way
> to be able to work with a project that you want to maven-shade-plugin some
> third party dependencies in, for use within and inside eclipse?
>
> Cleary I understand you can just package/install the shaded project into a
> repository then NOT bring in the source project into the workspace... but
> ideally I don't want that.
>
> Thanks!
>

maven-shade-plugin and Eclipse (m2e)

[Eddie Galvez]

What is the way to use the maven-shade-plugin but, what I think is the
obvious usage then of such a shaded project, to have it in eclipse as a
source project?

In other words - because maven-shade-plugin only does its thing on
package... while you are in Eclipse (your IDE), other projects will not
compile since they are expecting the shaded package names... what's the way
to be able to work with a project that you want to maven-shade-plugin some
third party dependencies in, for use within and inside eclipse?

Cleary I understand you can just package/install the shaded project into a
repository then NOT bring in the source project into the workspace... but
ideally I don't want that.

Thanks!