>
> What you have is a gwt-app that you use as a playground/sandbox to help
> you test gwt-libâ‹…s. It happens that the gwt-app was initialized from the
> archetype, but it could have not been the case and wouldn't have changed
> anything to your gwt-lib issue. It also happens that your gwt-app i
On Friday, April 27, 2018 at 9:36:04 PM UTC+2, vitrums wrote:
>
>
> If your lib does not have one single main gwt.xml entry point but really
>> is more like a gwt-user.jar "set of libraries", then you'd probably better
>> skip the gwt:generate-module and gwt:generate-module-metadata and *put
>
On Friday, April 27, 2018 at 7:38:41 PM UTC+3, Thomas Broyer wrote:
> - **
>>
>
> I must say I don't understand what you're talking about here (i.e. how
> you'd use them here)
>
In context of *maven-jar-plugin* I was simply referring to something like
e.g.
https://maven.apache.org/plugins/
On Friday, April 27, 2018 at 4:34:25 PM UTC+2, vitrums wrote:
>
> Any experienced developer tends to reuse existing components and organize
> his own code to allow reusability in future whenever it is possible.
> Division of labor further encourages a group of developers to physically
> split
Any experienced developer tends to reuse existing components and organize
his own code to allow reusability in future whenever it is possible.
Division of labor further encourages a group of developers to physically
split a big project into modules and work independently on each part. I
think T
